 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| hcs12 microcontrollers freescale.com mc9s12kg128 data sheet mc9s12kg128 rev. 1.15 06/2006
mc9s12kg128 data sheet mc9s12kg128v1 rev. rev. 1.15 06/2006 mc9s12kg128 data sheet, rev. 1.15 4 freescale semiconductor to provide the most up-to-date information, the revision of our documents on the world wide web will be the most current. your printed copy may be an earlier revision. to verify you have the latest information available, refer to: http://freescale.com/ the following revision history table summarizes changes contained in this document. revision history date revision level description oct 21, 2005 rev. 1.14 new data sheet jun 23, 2006 rev. 1.15 1. update pe0/pe1 pull up/down status in table 1_2 2. update vreg_3v3 v(lvia)/v(lvid) limit in table a-9 3. other minor update. freescale and the freescale logo are trademarks of freescale semiconductor, inc. this product incorporates superflash?technology licensed from sst. freescale semiconductor, inc., 2005,2006 all rights reserved. mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 5 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) . . . . . . . 19 chapter 2 128 kbyte ecc flash module (fts128k1eccv1) . . . . . . . . . . 75 chapter 3 2 kbyte eeprom module (eets2kv1). . . . . . . . . . . . . . . . . . 117 chapter 4 port integration module (pim9kg128v1) . . . . . . . . . . . . . . . . 137 chapter 5 clocks and reset generator (crgv4) . . . . . . . . . . . . . . . . . . 177 chapter 6 pierce oscillator (s12osclcpv1) . . . . . . . . . . . . . . . . . . . . . 213 chapter 7 analog-to-digital converter (atd10b16cv1) . . . . . . . . . . . . 219 chapter 8 inter-integrated circuit (iicv2) . . . . . . . . . . . . . . . . . . . . . . . . 247 chapter 9 freescale? scalable controller area network (mscanv2) . 271 chapter 10 serial communications interface (sciv1) . . . . . . . . . . . . . . . 325 chapter 11 serial peripheral interface (spiv3) . . . . . . . . . . . . . . . . . . . . . 357 chapter 12 pulse-width modulator (pwm8b8cv1). . . . . . . . . . . . . . . . . . 379 chapter 13 timer module (tim16b8cv1) . . . . . . . . . . . . . . . . . . . . . . . . . . 411 chapter 14 dual output voltage regulator (vreg3v3v2). . . . . . . . . . . . 437 chapter 15 background debug module (bdmv4). . . . . . . . . . . . . . . . . . . 445 chapter 16 debug module (dbgv1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 chapter 17 interrupt (intv1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 chapter 18 multiplexed external bus interface (mebiv3) . . . . . . . . . . . . 511 chapter 19 module mapping control (mmcv4) . . . . . . . . . . . . . . . . . . . . . 539 appendix a electrical characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 appendix b recommended pcb layout . . . . . . . . . . . . . . . . . . . . . . . . . . 592 appendix c package information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595 mc9s12kg128 data sheet, rev. 1.15 6 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 7 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) 1.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 1.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 1.1.3 mc9s12kg128 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 1.2 signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 1.2.1 signal properties summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 1.2.2 detailed signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 1.2.3 power supply pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 1.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 1.3.1 device memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 1.3.2 detailed register map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 1.3.3 part id assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66 1.4 system clock description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 1.5 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 1.5.1 chip con?uration summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 1.5.2 security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 1.5.3 low power modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 1.6 resets and interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 1.6.1 vectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 1.6.2 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 chapter 2 128 kbyte ecc flash module (fts128k1eccv1) 2.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 2.1.1 glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 2.1.2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 2.1.3 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .76 2.1.4 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 2.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 2.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77 2.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 2.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82 2.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 2.4.1 flash command operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 2.5 operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 2.5.1 wait mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 2.5.2 stop mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 2.5.3 background debug mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 mc9s12kg128 data sheet, rev. 1.15 8 freescale semiconductor 2.6 flash module security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 2.6.1 unsecuring the mcu using backdoor key access . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 2.6.2 unsecuring the flash module in special single-chip mode using bdm . . . . . . . . . . . 114 2.7 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 2.7.1 flash reset sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 14 2.7.2 reset while flash command active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 2.8 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 2.8.1 description of flash interrupt operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 chapter 3 2 kbyte eeprom module (eets2kv1) 3.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 3.1.1 glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 3.1.2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 3.1.3 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 18 3.1.4 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 3.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 3.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 18 3.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 3.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 3.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 3.4.1 program and erase operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 3.5 operating modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 3.5.1 wait mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 3.5.2 stop mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 3.5.3 background debug mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 3.6 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 3.7 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 chapter 4 port integration module (pim9kg128v1) 4.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 4.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 4.1.2 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138 4.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 4.2.1 signal properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 4.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 43 4.3.1 port t registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 4.3.2 port s registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 4.3.3 port m registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 4.3.4 port p registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 4.3.5 port h registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 4.3.6 port j registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 4.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 9 4.4.1 i/o register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 4.4.2 input register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 4.4.3 data direction register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 72 4.4.4 reduced drive register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 4.4.5 pull device enable register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 4.4.6 polarity select register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 4.4.7 pin con?uration summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 4.5 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 4.5.1 reset initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 4.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 4.6.1 general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 4.6.2 interrupt sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 4.6.3 operation in stop mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176 chapter 5 clocks and reset generator (crgv4) 5.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 5.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177 5.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 78 5.1.3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 5.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 5.2.1 v ddpll , v sspll ?pll operating voltage, pll ground . . . . . . . . . . . . . . . . . . . . . . 179 5.2.2 xfc ?pll loop filter pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179 5.2.3 reset ?reset pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 5.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 80 5.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 5.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 5.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 5.4.1 phase locked loop (pll) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192 5.4.2 system clocks generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 5.4.3 clock monitor (cm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 6 5.4.4 clock quality checker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 6 5.4.5 computer operating properly watchdog (cop) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 5.4.6 real-time interrupt (rti) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 5.4.7 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 99 5.4.8 low-power operation in run mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 5.4.9 low-power operation in wait mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 5.4.10 low-power operation in stop mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 5.5 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 5.5.1 clock monitor reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 10 5.5.2 computer operating properly watchdog (cop) reset . . . . . . . . . . . . . . . . . . . . . . . . . 210 5.5.3 power-on reset, low voltage reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211 5.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 5.6.1 real-time interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 5.6.2 pll lock interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 mc9s12kg128 data sheet, rev. 1.15 10 freescale semiconductor 5.6.3 self-clock mode interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 chapter 6 pierce oscillator (s12osclcpv1) 6.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 6.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213 6.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 13 6.1.3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 6.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 6.2.1 v ddpll and v sspll ?operating and ground voltage pins . . . . . . . . . . . . . . . . . . . . 214 6.2.2 extal and xtal ?input and output pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214 6.2.3 xclks ?input signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 6.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 16 6.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 6.4.1 gain control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 6.4.2 clock monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 6.4.3 wait mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 7 6.4.4 stop mode operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 7 chapter 7 analog-to-digital converter (atd10b16cv1) 7.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 7.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 7.1.2 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 7.1.3 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 21 7.2 signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 7.2.1 detailed signal descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 7.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 22 7.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 7.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 7.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 7.4.1 analog sub-block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243 7.4.2 digital sub-block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 7.5 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 7.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 11 chapter 8 inter-integrated circuit (iicv2) 8.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 8.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247 8.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 48 8.1.3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248 8.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 8.2.1 iic_scl ?serial clock line pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 8.2.2 iic_sda ?serial data line pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 8.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 49 8.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 8.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 8.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 8.4.1 i-bus protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261 8.4.2 operation in run mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 8.4.3 operation in wait mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 8.4.4 operation in stop mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264 8.5 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 8.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 8.7 initialization/application information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 8.7.1 iic programming examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 chapter 9 freescale? scalable controller area network (mscanv2) 9.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 9.1.1 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 9.1.2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 9.1.3 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 72 9.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 9.2.1 rxcan ?can receiver input pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 9.2.2 txcan ?can transmitter output pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 9.2.3 can system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 9.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 73 9.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 9.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 9.3.3 programmer s model of message storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297 9.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 9.4.1 general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305 9.4.2 message storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306 9.4.3 identi?r acceptance filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 309 9.4.4 timer link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315 9.4.5 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 16 9.4.6 low-power options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 6 9.4.7 reset initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 mc9s12kg128 data sheet, rev. 1.15 12 freescale semiconductor 9.4.8 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 9.5 initialization/application information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 9.5.1 mscan initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3 chapter 10 serial communications interface (sciv1) 10.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 10.1.1 glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 10.1.2 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325 10.1.3 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 10.1.4 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 10.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 10.2.1 txd-sci transmit pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 10.2.2 rxd-sci receive pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327 10.3 memory map and registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 10.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 10.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328 10.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 10.4.1 data format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 10.4.2 baud rate generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 38 10.4.3 transmitter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 10.4.4 receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342 10.4.5 single-wire operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 10.4.6 loop operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 10.5 initialization information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 10.5.1 reset initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351 10.5.2 interrupt operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352 10.5.3 recovery from wait mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 chapter 11 serial peripheral interface (spiv3) 11.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 11.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 11.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 11.1.3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 11.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 11.2.1 mosi ?master out/slave in pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358 11.2.2 miso ?master in/slave out pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.2.3 ss ?slave select pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.2.4 sck ?serial clock pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 11.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360 11.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 13 11.4.1 master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368 11.4.2 slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 11.4.3 transmission formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 70 11.4.4 spi baud rate generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 11.4.5 special features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 11.4.6 error conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375 11.4.7 operation in run mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 11.4.8 operation in wait mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 6 11.4.9 operation in stop mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 6 11.5 reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 11.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 11.6.1 modf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 11.6.2 spif . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 11.6.3 sptef . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 chapter 12 pulse-width modulator (pwm8b8cv1) 12.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 12.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 12.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 12.1.3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 12.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 12.2.1 pwm7 ?pwm channel 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 12.2.2 pwm6 ?pwm channel 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380 12.2.3 pwm5 ?pwm channel 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.4 pwm4 ?pwm channel 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.5 pwm3 ?pwm channel 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.6 pwm3 ?pwm channel 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.7 pwm3 ?pwm channel 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.2.8 pwm3 ?pwm channel 0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 12.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 12.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 12.4.1 pwm clock select . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 12.4.2 pwm channel timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 12.5 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408 12.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 mc9s12kg128 data sheet, rev. 1.15 14 freescale semiconductor chapter 13 timer module (tim16b8cv1) 13.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 13.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 13.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 13.1.3 block diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412 13.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414 13.2.1 ioc7 ?input capture and output compare channel 7 pin . . . . . . . . . . . . . . . . . . . . 414 13.2.2 ioc6 ?input capture and output compare channel 6 pin . . . . . . . . . . . . . . . . . . . . 414 13.2.3 ioc5 ?input capture and output compare channel 5 pin . . . . . . . . . . . . . . . . . . . . 414 13.2.4 ioc4 ?input capture and output compare channel 4 pin . . . . . . . . . . . . . . . . . . . . 414 13.2.5 ioc3 ?input capture and output compare channel 3 pin . . . . . . . . . . . . . . . . . . . . 414 13.2.6 ioc2 ?input capture and output compare channel 2 pin . . . . . . . . . . . . . . . . . . . . 415 13.2.7 ioc1 ?input capture and output compare channel 1 pin . . . . . . . . . . . . . . . . . . . . 415 13.2.8 ioc0 ?input capture and output compare channel 0 pin . . . . . . . . . . . . . . . . . . . . 415 13.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 13.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 13.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 13.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431 13.4.1 prescaler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432 13.4.2 input capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 13.4.3 output compare . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 13.4.4 pulse accumulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433 13.4.5 event counter mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 34 13.4.6 gated time accumulation mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 13.5 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 13.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434 13.6.1 channel [7:0] interrupt (c[7:0]f) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 13.6.2 pulse accumulator input interrupt (paovi) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 13.6.3 pulse accumulator over?w interrupt (paovf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 13.6.4 timer over?w interrupt (tof) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435 chapter 14 dual output voltage regulator (vreg3v3v2) 14.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 14.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 14.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437 14.1.3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438 14.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 14.2.1 v ddr ?regulator power input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 14.2.2 v dda , v ssa ?regulator reference supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439 14.2.3 v dd , v ss ?regulator output1 (core logic) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 14.2.4 v ddpll , v sspll ?regulator output2 (pll) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 14.2.5 v regen ?optional regulator enable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 15 14.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 14.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440 14.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 14.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 14.4.1 reg ?regulator core . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441 14.4.2 full-performance mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.3 reduced-power mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.4 lvd ?low-voltage detect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.5 por ?power-on reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.6 lvr ?low-voltage reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.4.7 ctrl ?regulator control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442 14.5 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 14.5.1 power-on reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 14.5.2 low-voltage reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 14.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 14.6.1 lvi ?low-voltage interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443 chapter 15 background debug module (bdmv4) 15.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 15.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445 15.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 15.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446 15.2.1 bkgd ?background interface pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 15.2.2 t a ghi ?high byte instruction tagging pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 15.2.3 t a glo ?low byte instruction tagging pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447 15.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 15.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448 15.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449 15.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 15.4.1 security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 15.4.2 enabling and activating bdm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454 15.4.3 bdm hardware commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455 15.4.4 standard bdm firmware commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456 15.4.5 bdm command structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457 15.4.6 bdm serial interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459 15.4.7 serial interface hardware handshake protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462 15.4.8 hardware handshake abort procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464 15.4.9 sync ?request timed reference pulse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 15.4.10instruction tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467 15.4.11instruction tagging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 15.4.12serial communication time-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468 15.4.13operation in wait mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 15.4.14operation in stop mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 69 mc9s12kg128 data sheet, rev. 1.15 16 freescale semiconductor chapter 16 debug module (dbgv1) 16.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 16.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471 16.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 16.1.3 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473 16.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475 16.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 16.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 16.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476 16.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 16.4.1 dbg operating in bkp mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491 16.4.2 dbg operating in dbg mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493 16.4.3 breakpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500 16.5 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 16.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501 chapter 17 interrupt (intv1) 17.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503 17.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 17.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504 17.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 17.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 17.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 17.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505 17.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507 17.4.1 low-power modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 07 17.5 resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 17.6 interrupts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 17.6.1 interrupt registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 17.6.2 highest priority i-bit maskable interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508 17.6.3 interrupt priority decoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 08 17.7 exception priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509 mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 17 chapter 18 multiplexed external bus interface (mebiv3) 18.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 18.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511 18.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 18.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 18.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 18.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 18.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516 18.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 18.4.1 detecting access type from external signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532 18.4.2 stretched bus cycles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 18.4.3 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533 18.4.4 internal visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538 18.4.5 low-power options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 38 chapter 19 module mapping control (mmcv4) 19.1 introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539 19.1.1 features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.1.2 modes of operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.2 external signal description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.3 memory map and register de?ition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.3.1 module memory map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540 19.3.2 register descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542 19.4 functional description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 19.4.1 bus control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551 19.4.2 address decoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552 19.4.3 memory expansion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 53 mc9s12kg128 data sheet, rev. 1.15 18 freescale semiconductor appendix a electrical characteristics a.1 general . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 a.1.1 parameter classification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 a.1.2 power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559 a.1.3 pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 a.1.4 current injection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560 a.1.5 absolute maximum ratings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561 a.1.6 esd protection and latch-up immunity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562 a.1.7 operating conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563 a.1.8 power dissipation and thermal characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564 a.1.9 i/o characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566 a.1.10 supply currents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568 a.2 voltage regulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570 a.3 chip power-up and lvi/lvr graphical explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571 a.4 output loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 a.4.1 resistive loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 a.4.2 capacitive loads. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572 a.5 atd characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 a.5.1 atd operating characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573 a.5.2 factors influencing accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574 a.5.3 atd accuracy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575 a.6 nvm, flash and eeprom. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 a.6.1 nvm timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 578 a.6.2 nvm reliability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580 a.7 reset, oscillator and pll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 a.7.1 startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581 a.7.2 oscillator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582 a.7.3 phase locked loop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583 a.8 mscan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 a.9 spi . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 a.9.1 master mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586 a.9.2 slave mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 a.10 external bus timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589 a.10.1 general muxed bus timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589 appendix b recommended pcb layout appendix c package information c.1 112-pin lqfp package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596 c.2 80-pin qfp package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597 mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 19 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) 1.1 introduction the mc9s12kg128 is a 112/80 pin 16-bit flash-based microcontroller family targeted for high reliability systems. the mc9s12kg128 has an increased performance in reliability over the life of the product due to a built-in error checking and correction code (ecc) in the flash memory. the program and erase operations automatically generate six parity bits per word making ecc transparent to the user. the mc9s12kg128 is comprised of standard on-chip peripherals including a 16-bit central processing unit (cpu12), 128k bytes of flash eeprom, 2k bytes of eeprom, 8k bytes of ram, two asynchronous serial communications interface (sci), three serial peripheral interface (spi), iic-bus, an 8-channel ic/oc timer, one 16-channel 10-bit analog-to-digital converter (adc), an 8-channel pulse-width modulator (pwm), two can 2.0 a, b software compatible modules, 29 discrete digital i/o channels (port a, port b, port e and port k), and 20 discrete digital i/o lines with interrupt and wakeup capability. the mc9s12kg128 has full 16-bit data paths throughout, however, the external bus can operate in an 8-bit narrow mode so single 8-bit wide memory can be interfaced for lower cost systems. the inclusion of a pll circuit allows power consumption and performance to be adjusted to suit operational requirements. 1.1.1 features hcs12 core 16-bit hcs12 cpu upward compatible with m68hc11 instruction set interrupt stacking and programmer s model identical to m68hc11 instruction queue enhanced indexed addressing mebi (multiplexed external bus interface) mmc (memory map and interface) int (interrupt controller) dbg (debugger) bdm (background debug mode) oscillator 4mhz to 16mhz frequency range pierce with amplitude loop control clock monitor chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 20 freescale semiconductor clock and reset generator (crg) phase-locked loop clock frequency multiplier self clock mode in absence of external clock cop watchdog real time interrupt (rti) memory 128k byte flash eeprom internal program/erase voltage generation security and block protect bits hamming error correction coding (ecc) 2k byte eeprom 8k byte static ram single-cycle misaligned word accesses without wait states analog-to-digital converter (adc) one 16-channel module with 10-bit resolution external conversion trigger capability 8-channel timer (tim) programmable input capture or output compare channels simple pwm mode counter modulo reset external event counting gated time accumulation 8-channel pulse width modulator (pwm) programmable period and duty cycle per channel 8-bit 8-channel or 16-bit 4-channel edge and center aligned pwm signals emergency shutdown input two 1m bit per second, can 2.0 a, b software compatible modules five receive and three transmit buffers flexible identi?r ?ter programmable as 2 x 32 bit, 4 x 16 bit or 8 x 8 bit four separate interrupt channels for rx, tx, error and wake-up low-pass ?ter wake-up function loop-back for self test operation serial interfaces two asynchronous serial communication interface (sci) three synchronous serial peripheral interface (spi) inter-ic bus (iic) internal 2.5v regulator input voltage range from 3.15v to 5.5v chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 21 low power mode capability low voltage reset (lvr) and low voltage interrupt (lvi) 20 key wake up inputs rising or falling edge triggered interrupt capability digital ?ter to prevent short pulses from triggering interrupts programmable pull ups and pull downs operating frequency for ambient temperatures (t a - 40 c to 125 c) 50mhz equivalent to 25mhz bus speed 112-pin lqfp or 80-pin qfp package i/o lines with 3.3v/5v input and drive capability 3.3v/5v a/d converter inputs 1.1.2 modes of operation normal modes normal single-chip mode normal expanded wide mode normal expanded narrow mode emulation expanded wide mode emulation expanded narrow mode special operating modes special single-chip mode with active background debug mode special test mode (freescale use only) special peripheral mode (freescale use only) each of the above modes of operation can be con?ured for three low power submodes stop mode pseudo stop mode wait mode secure operation, preventing the unauthorized read and write of the memory contents. chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 22 freescale semiconductor table 1-1 shows a feature overview of the mc9s12kg128 members. figure 1-1 shows the part number coding based on the package and temperature options for the mc9s12kg128. figure 1-1. order part number coding table 1-1. list of mc9s12kg128 members device temp options 1 1 c: ta = 85?c, f = 25mhz. v: ta=105?c, f = 25mhz. m: ta= 125?c, f = 25mhz flash ram eeprom package can sci spi iic a/d 2 2 number of channels pwm 2 tim 2 i/o 3 3 i/o is the sum of ports capable to act as digital input or output. mc9s12kg128 c, v, m 128k 8k 2k 112 lqfp 2 2 3 1 16 8 8 91 80 qfp 2 2 3 1 8 7 8 59 mc9s12kl128 c, v, m 128k 6k 2k 112 lqfp 1 2 2 1 16 8 8 91 80 qfp 1 1 2 1 8 7 8 59 mc9s12kl64 c, v, m 64k 4k 1k 112 lqfp 1 2 2 1 16 8 8 91 80 qfp 1 1 2 1 8 7 8 59 mc9s12kl32 c, v, m 32k 2k 1k 80 qfp 1 1 2 1 8 7 8 59 mc9s12kc128 c, v, m 128k 6k none 112 lqfp 1 2 2 1 16 8 8 91 80 qfp 1 1 2 1 8 7 8 59 mc9s12kc64 c, v, m 64k 4k none 112 lqfp 1 2 2 1 16 8 8 91 80 qfp 1 1 2 1 8 7 8 59 mc9s12 kg128 c fu package option temperature option device title controller family temperature options c = -40?c to 85?c v = -40?c to 105?c m = -40?c to 125?c package options pv = 112lqfp fu = 80qfp chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 23 1.1.3 mc9s12kg128 block diagram figure 1-2. mc9s12kg128 block diagram 128k byte flash eeprom 8k byte ram reset extal xtal vdd1,2 vss1,2 sci0 bkgd r/ w modb xirq noacc/ xclks system integration module (sim) vddr cpu12 periodic interrupt cop watchdog clock monitor single-wire bdm breakpoints pll vsspll xfc vddpll multiplexed address/data bus at d multiplexed wide bus multiplexed vddx vssx internal logic 2.5v narrow bus ppage vddpll vsspll osc/pll 2.5v irq lstrb eclk moda pa 4 pa 3 pa 2 pa 1 pa 0 pa 7 pa 6 pa 5 test addr12 addr11 addr10 addr9 addr8 addr15 addr14 addr13 data12 data11 data10 data9 data8 data15 data14 data13 pb4 pb3 pb2 pb1 pb0 pb7 pb6 pb5 addr4 addr3 addr2 addr1 addr0 addr7 addr6 addr5 data4 data3 data2 data1 data0 data7 data6 data5 data4 data3 data2 data1 data0 data7 data6 data5 pe3 pe4 pe5 pe6 pe7 pe0 pe1 pe2 an02 an06 an00 an07 an01 an03 an04 an05 pad03 pad04 pad05 pad06 pad07 pad00 pad01 pad02 ioc2 ioc6 ioc0 ioc7 ioc1 ioc3 ioc4 ioc5 pt3 pt4 pt5 pt6 pt7 pt0 pt1 pt2 vrh vrl vdda vssa vrh vrl an10 an14 an08 an15 an09 an11 an12 an13 pad11 pad12 pad13 pad14 pad15 pad08 pad09 pad10 vdda vssa rxd txd miso mosi ps3 ps4 ps5 ps0 ps1 ps2 sci1 rxd txd pwm2 pwm6 pwm0 pwm7 pwm1 pwm3 pwm4 pwm5 pp3 pp4 pp5 pp6 pp7 pp0 pp1 pp2 pix2 pix0 pix1 pix3 ecs pk3 pk7 pk0 pk1 xaddr17 ecs xaddr14 xaddr15 xaddr16 sck ss ps6 ps7 spi0 iic sda scl pj6 pj7 can0 rxcan txcan pm1 pm0 pm2 pm3 pm4 pm5 pm6 pm7 kwh2 kwh6 kwh0 kwh7 kwh1 kwh3 kwh4 kwh5 ph3 ph4 ph5 ph6 ph7 ph0 ph1 ph2 kwj0 kwj1 pj0 pj1 i/o driver 3.3v/5v vdda vssa a/d converter 3.3v/5v ddra ddrb pta ptb ddre pte pa d pa d ptk ddrk ptt ddrt ptp ddrp pts ddrs ptm ddrm pth ddrh ptj ddrj pk2 crg voltage regulator vssr vdd1,2 vss1,2 vregen vddr vssr voltage regulator 3.3v/5v pix4 pix5 pk4 pk5 xaddr18 xaddr19 voltage reference kwp2 kwp6 kwp0 kwp7 kwp1 kwp3 kwp4 kwp5 kwj6 kwj7 tim signals shown in bold are not available on n the 80-pin package module to port routing 2k byte eeprom pwm miso mosi sck ss spi1 miso mosi sck ss spi2 can4 rxcan txcan osc debugger chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 24 freescale semiconductor 1.2 signal description the mc9s12kg128 is available in a 112-pin low pro?e quad ?t pack (lqfp) and a 80-pin quad ?t pack (qfp). most pins perform two or more functions, as described in section 1.2.1, ?ignal properties summary . figure 1-3 and figure 1-4 show the pin assignments for different packages. figure 1-3. pin assignments for 112 lqfp vrh vdda pad15/an15 pad07/an07 pad14/an14 pad06/an06 pad13/an13 pad05/an05 pad12/an12 pad04/an04 pad11/an11 pad03/an03 pad10/an10 pad02/an02 pad09/an09 pad01/an01 pad08/an08 pad00/an00 vss2 vdd2 pa7/addr15/data15 pa6/addr14/data14 pa5/addr13/data13 pa4/addr12/data12 pa3/addr11/data11 pa2/addr10/data10 pa1/addr9/data9 pa0/addr8/data8 pp4/kwp4/pwm4/miso2 pp5/kwp5/pwm5/mosi2 pp6/kwp6/pwm6/ ss2 pp7/kwp7/pwm7/sck2 pk7/ ecs vddx vssx pm0/rxcan0 pm1/txcan0 pm2/rxcan0/miso0 pm3/txcan0/ ss0 pm4/rxcan0/rxcan4/mosi0 pm5/txcan0/txcan4/sck0 pj6/kwj6/rxcan4/sda pj7/kwj7/txcan4/scl vregen ps7/ ss0 ps6/sck0 ps5/mosi0 ps4/miso0 ps3/txd1 ps2/rxd1 ps1/txd0 ps0/rxd0 pm6/rxcan4 pm7/txcan4 vssa vrl ss1/pwm3/kwp3/pp3 sck1/pwm2/kwp2/pp2 mosi1/pwm1/kwp1/pp1 miso1/pwm0/kwp0/pp0 xaddr17/pk3 xaddr16/pk2 xaddr15/pk1 xaddr14/pk0 ioc0/pt0 ioc1/pt1 ioc2/pt2 ioc3/pt3 vdd1 vss1 ioc4/pt4 ioc5/pt5 ioc6/pt6 ioc7/pt7 xaddr19/pk5 xaddr18/pk4 kwj1/pj1 kwj0/pj0 modc/ t a ghi/bkgd addr0/data0/pb0 addr1/data1/pb1 addr2/data2/pb2 addr3/data3/pb3 addr4/data4/pb4 addr5/data5/pb5 addr6/data6/pb6 addr7/data7/pb7 ss2/kwh7/ph7 sck2/kwh6/ph6 mosi2/kwh5/ph5 miso2/kwh4/ph4 xclks/noacc/pe7 modb/ipipe1/pe6 moda/ipipe0/pe5 eclk/pe4 vssr vddr reset vddpll xfc vsspll extal xtal test ss1/kwh3/ph3 sck1/kwh2/ph2 mosi1/kwh1/ph1 miso1/kwh0/ph0 lstrb/ t a glo/pe3 r/ w/pe2 irq/pe1 xirq/pe0 signals shown in bold are not available on the 80-pin package mc9s12kg128 112lqfp 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 25 figure 1-4. pin assignments for 80 qfp 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 vrh vdda pad07/an07 pad06/an06 pad05/an05 pad04/an04 pad03/an03 pad02/an02 pad01/an01 pad00/an00 vss2 vdd2 pa7/addr15/data15 pa6/addr14/data14 pa5/addr13/data13 pa4/addr12/data12 pa3/addr11/data11 pa2/addr10/data10 pa1/addr9/data9 pa0/addr8/data8 pp4/kwp4/pwm4/miso2 pp5/kwp5/pwm5/mosi2 pp7/kwp7/pwm7/sck2 vddx vssx pm0/rxcan0 pm1/txcan0 pm2/rxcan0/miso0 pm3/txcan0/ ss0 pm4/rxcan0/rxcan4/mosi 0 pm5/txcan0/txcan4/sck0 pj6/kwj6/rxcan4/sda pj7/kwj7/txcan4/scl vregen ps3/txd1 ps2/rxd1 ps1/txd0 ps0/rxd0 vssa vrl pwm3/kwp3/pp3 pwm2/kwp2/pp2 pwm1/kwp1/pp1 pwm0/kwp0/pp0 ioc0/pt0 ioc1/pt1 ioc2/pt2 ioc3/pt3 vdd1 vss1 ioc4/pt4 ioc5/pt5 ioc6/pt6 ioc7/pt7 modc/ t a ghi/bkgd addr0/data0/pb0 addr1/data1/pb1 addr2/data2/pb2 addr3/data3/pb3 addr4/data4/pb4 addr5/data5/pb5 addr6/data6/pb6 addr7/data7/pb7 xclks/noacc/pe7 modb/ipipe1/pe6 moda/ipipe0/pe5 eclk/pe4 vssr vddr reset vddpll xfc vsspll extal xtal test lstrb/ t a glo/pe3 r/ w/pe2 irq/pe1 xirq/pe0 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 mc9s12kg128 80 qfp chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 26 freescale semiconductor 1.2.1 signal properties summary table 1-2 summarizes the pin functionality. signals shown in bold are not available in the 80-pin package. table 1-3 summarizes the power and ground pins. table 1-2. signal properties (sheet 1 of 3) pin name function 1 pin name function 2 pin name function 3 pin name function 4 powered by internal pull resistor description ctrl reset state extal vddpll na na oscillator pins xtal vddpll na na reset vddr none none external reset test na na na test input vregen vddx na na voltage regulator enable input xfc vddpll na na pll loop filter bkgd t a ghi modc vddr always up up background debug, tag high, mode input pad[15:8] an[15:8] vdda none none port ad input, analog inputs of atd pad[7:0] an[7:0] vdda none none port ad input, analog inputs of at d pa[7:0] addr[15:8]/ data[15:8] vddr pucr disabled port a i/o, multiplexed address/data pb[7:0] addr[7:0]/ data[7:0] vddr pucr disabled port b i/o, multiplexed address/data pe7 noacc xclks vddr pucr up port e i/o, access, clock select pe6 ipipe1 modb vddr while reset pin is low: down port e i/o, pipe status, mode input pe5 ipipe0 moda vddr while reset pin is low: down port e i/o, pipe status, mode input pe4 eclk vddr pucr up port e i/o, bus clock output pe3 lstrb t a glo vddr pucr up port e i/o, byte strobe, tag low pe2 r/ w vddr pucr up port e i/o, r/ w in expanded modes pe1 irq vddr pucr up port e input, maskable interrupt pe0 xirq vddr pucr up port e input, non maskable interrupt ph7 kwh7 ss2 vddr perh/ ppsh disabled port h i/o, interrupt, ss of spi2 ph6 kwh6 sck2 vddr perh/ ppsh disabled port h i/o, interrupt, sck of spi2 ph5 kwh5 mosi2 vddr perh/ ppsh disabled port h i/o, interrupt, mosi of spi2 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 27 ph4 kwh4 miso2 vddr perh/ ppsh disabled port h i/o, interrupt, miso of spi2 ph3 kwh3 ss1 vddr perh/ ppsh disabled port h i/o, interrupt, ss of spi1 ph2 kwh2 sck1 vddr perh/ ppsh disabled port h i/o, interrupt, sck of spi1 ph1 kwh1 mosi1 vddr perh/ ppsh disabled port h i/o, interrupt, mosi of spi1 ph0 kwh0 miso1 vddr perh/ ppsh disabled port h i/o, interrupt, miso of spi1 pj7 kwj7 txcan4 scl vddx perj/ ppsj up port j i/o, interrupt, tx of can4, scl of iic pj6 kwj6 rxcan4 sda vddx perj/ ppsj up port j i/o, interrupt, rx of can4, sda of iic pj[1:0] kwj[1:0] vddx perj/ ppsj up port j i/o, interrupts pk7 ecs romctl vddx pucr up port k i/o, emulation chip select, rom on enable pk[5:0] xaddr[19:14] vddx pucr up port k i/o, extended addresses pm7 txcan4 vddx perm/ ppsm disabled port m i/o, can4 tx pm6 rxcan4 vddx perm/ ppsm disabled port m i/o, can4 rx pm5 txcan0 txcan4 sck0 vddx perm/ ppsm disabled port m i/o, can0 tx, can4 tx, spi0 sck pm4 rxcan0 rxcan4 mosi0 vddx perm/ ppsm disabled port m i/o, can0 rx, can4 rx, spi0 mosi pm3 txcan0 ss0 vddx perm/ ppsm disabled port m i/o, can0 tx, spi0 ss pm2 rxcan0 miso0 vddx perm/ ppsm disabled port m i/o, can0 rx, spi0 miso pm1 txcan0 vddx perm/ ppsm disabled port m i/o, can0 tx pm0 rxcan0 vddx perm/ ppsm disabled port m i/o, can0 rx pp7 kwp7 pwm7 sck2 vddx perp/ ppsp disabled port p i/o, interrupt, pwm channel 7, sck of spi2 pp6 kwp6 pwm6 ss2 vddx perp/ ppsp disabled port p i/o, interrupt, pwm channel 6, spi2 ss table 1-2. signal properties (sheet 2 of 3) pin name function 1 pin name function 2 pin name function 3 pin name function 4 powered by internal pull resistor description ctrl reset state chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 28 freescale semiconductor pp5 kwp5 pwm5 mosi2 vddx perp/ ppsp disabled port p i/o, interrupt, pwm channel 5, spi2 mosi pp4 kwp4 pwm4 miso2 vddx perp/ ppsp disabled port p i/o, interrupt, pwm channel 4, spi2 miso pp3 kwp3 pwm3 ss1 vddx perp/ ppsp disabled port p i/o, interrupt, pwm channel 3, spi1 ss pp2 kwp2 pwm2 sck1 vddx perp/ ppsp disabled port p i/o, interrupt, pwm channel 2, spi1 sck pp1 kwp1 pwm1 mosi1 vddx perp/ ppsp disabled port p i/o, interrupt, pwm channel 1, spi1 mosi pp0 kwp0 pwm0 miso1 vddx perp/ ppsp disabled port p i/o, interrupt, pwm channel 0, spi1 miso ps7 ss0 vddx pers/ ppss up port s i/o, spi0 ss ps6 sck0 vddx pers/ ppss up port s i/o, spi0 sck ps5 mosi0 vddx pers/ ppss up port s i/o, spi0 mosi ps4 miso0 vddx pers/ ppss up port s i/o, spi0 miso ps3 txd1 vddx pers/ ppss up port s i/o, sci1txd ps2 rxd1 vddx pers/ ppss up port s i/o, sci1rxd ps1 txd0 vddx pers/ ppss up port s i/o, sci0 txd ps0 rxd0 vddx pers/ ppss up port s i/o, sci0 rxd pt[7:0] ioc[7:0] vddx up or down disabled port t i/o, timer channels table 1-2. signal properties (sheet 3 of 3) pin name function 1 pin name function 2 pin name function 3 pin name function 4 powered by internal pull resistor description ctrl reset state chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 29 note all vss pins must be connected together in the application. because fast signal transitions place high, short-duration current demands on the power supply, use bypass capacitors with high-frequency characteristics and place them as close to the mcu as possible. bypass requirements depend on mcu pin load. 1.2.2 detailed signal descriptions 1.2.2.1 extal, xtal ?oscillator pins extal and xtal are the crystal driver and external clock pins. on reset all the device clocks are derived from the extal input frequency. xtal is the crystal output. 1.2.2.2 reset ?external reset pin an active low bidirectional control signal, it acts as an input to initialize the mcu to a known start-up state, and an output when an internal mcu function causes a reset. 1.2.2.3 test ?test pin this input only pin is reserved for test. note the test pin must be tied to vss in all applications. table 1-3. power and ground mnemonic nominal voltage description vdd1 vdd2 2.5 v internal power and ground generated by internal regulator. these also allow an external source to supply the core vdd/vss voltages and bypass the internal voltage regulator. vss1 vss2 0v vddr 3.3/5.0 v external power and ground, supply to pin drivers and internal voltage regulator. vssr 0 v vddx 3.3/5.0 v external power and ground, supply to pin drivers. vssx 0 v vdda 3.3/5.0 v operating voltage and ground for the analog-to-digital converter and the reference for the internal voltage regulator, allows the supply voltage to the a/d to be bypassed independently. vssa 0 v vrh 3.3/5.0 v reference voltage high for the atd converter. vrl 0 v reference voltage low for the atd converter. vddpll 2.5 v provides operating voltage and ground for the phased-locked loop. this allows the supply voltage to the pll to be bypassed independently. internal power and ground generated by internal regulator. vsspll 0 v chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 30 freescale semiconductor 1.2.2.4 vregen ?voltage regulator enable pin this input only pin enables or disables the on-chip voltage regulator. 1.2.2.5 xfc ?pll loop filter pin pll loop ?ter. please ask your freescale representative for the interactive application note to compute pll loop ?ter elements. any current leakage on this pin must be avoided. figure 1-5. pll loop filter connections 1.2.2.6 bkgd / t a ghi / modc ?background debug, tag high, and mode pin the bkgd/ t a ghi/modc pin is used as a pseudo-open-drain pin for the background debug communication. in mcu expanded modes of operation when instruction tagging is on, an input low on this pin during the falling edge of e-clock tags the high half of the instruction word being read into the instruction queue. it is used as a mcu operating mode select pin during reset. the state of this pin is latched to the modc bit at the rising edge of reset. 1.2.2.7 pad[15:0] / an[15:0] ?port ad input pins pad15 - pad0 are general purpose input pins and analog inputs of the analog to digital converter with 16 channels (atd). 1.2.2.8 pa[7:0] / addr[15:8] / data[15:8] ?port a i/o pins pa7?a0 are general purpose input or output pins. in mcu expanded modes of operation, these pins are used for the multiplexed external address and data bus. 1.2.2.9 pb[7:0] / addr[7:0] / data[7:0] ?port b i/o pins pb7?b0 are general purpose input or output pins. in mcu expanded modes of operation, these pins are used for the multiplexed external address and data bus. 1.2.2.10 pe7 / noacc / xclks ?port e i/o pin 7 pe7 is a general purpose input or output pin. during mcu expanded modes of operation, the noacc signal, when enabled, is used to indicate that the current bus cycle is an unused or ?ree cycle. this signal will assert when the cpu is not using the bus. mcu xfc r cs cp vddpll vddpll chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 31 the xclks is an input signal which controls whether a crystal in combination with the internal loop controlled pierce (low power) oscillator is used or whether full swing pierce oscillator/external clock circuitry is used. the state of this pin is latched at the rising edge of reset. if the input is a logic low the extal pin is con?ured for an external clock drive or full swing pierce oscillator. if input is a logic high a loop controlled pierce oscillator circuit is con?ured on extal and xtal. since this pin is an input with a pull-up device during reset, if the pin is left ?ating, the default con?uration is a loop controlled pierce oscillator circuit on extal and xtal. figure 1-6. loop controlled pierce oscillator connections (pe7 = 1) figure 1-7. full swing pierce oscillator connections (pe7 = 0) table 1-4. clock selection based on pe7 during reset pe7 description 1 loop controlled pierce oscillator selected 0 full swing pierce oscillator or external clock selected mcu extal xtal vsspll crystal or ceramic c8 c7 resonator * rs can be zero (shorted) when use with higher frequency crystals. refer to manufacturer s data. mcu extal xtal rs* rb vsspll c8 c7 crystal or ceramic resonator chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 32 freescale semiconductor figure 1-8. external clock connections (pe7 = 0) 1.2.2.11 pe6 / modb / ipipe1 ?port e i/o pin 6 pe6 is a general purpose input or output pin. it is used as a mcu operating mode select pin during reset. the state of this pin is latched to the modb bit at the rising edge of reset. this pin is shared with the instruction queue tracking signal ipipe1. 1.2.2.12 pe5 / moda / ipipe0 ?port e i/o pin 5 pe5 is a general purpose input or output pin. it is used as a mcu operating mode select pin during reset. the state of this pin is latched to the moda bit at the rising edge of reset. this pin is shared with the instruction queue tracking signal ipipe0. 1.2.2.13 pe4 / eclk ?port e i/o pin 4 pe4 is a general purpose input or output pin. it can be con?ured to drive the internal bus clock eclk. eclk can be used as a timing reference. 1.2.2.14 pe3 / lstrb / t a glo ?port e i/o pin 3 pe3 is a general purpose input or output pin. in mcu expanded modes of operation, lstrb can be used for the low-byte strobe function to indicate the type of bus access and when instruction tagging is on, t a glo is used to tag the low half of the instruction word being read into the instruction queue. 1.2.2.15 pe2 / r/ w port e i/o pin 2 pe2 is a general purpose input or output pin. in mcu expanded modes of operations, this pin drives the read/write output signal for the external bus. it indicates the direction of data on the external bus. 1.2.2.16 pe1 / irq ?port e input pin 1 pe1 is a general purpose input pin and the maskable interrupt request input that provides a means of applying asynchronous interrupt requests. this will wake up the mcu from stop or wait mode. mcu extal xtal cmos-compatible external oscillator not connected (vddpll-level) chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 33 1.2.2.17 pe0 / xirq ?port e input pin 0 pe0 is a general purpose input pin and the non-maskable interrupt request input that provides a means of applying asynchronous interrupt requests. this will wake up the mcu from stop or wait mode. 1.2.2.18 ph7 / kwh7 / ss2 ?port h i/o pin 7 ph7 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as slave select pin ss of the serial peripheral interface 2 (spi2). 1.2.2.19 ph6 / kwh6 / sck2 ?port h i/o pin 6 ph6 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as serial clock pin sck of the serial peripheral interface 2 (spi2). 1.2.2.20 ph5 / kwh5 / mosi2 ?port h i/o pin 5 ph5 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as master output (during master mode) or slave input pin (during slave mode) mosi of the serial peripheral interface 2 (spi2). 1.2.2.21 ph4 / kwh4 / miso2 ?port h i/o pin 2 ph4 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as master input (during master mode) or slave output (during slave mode) pin miso of the serial peripheral interface 2 (spi2). 1.2.2.22 ph3 / kwh3 / ss1 ?port h i/o pin 3 ph3 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as slave select pin ss of the serial peripheral interface 1 (spi1). 1.2.2.23 ph2 / kwh2 / sck1 ?port h i/o pin 2 ph2 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as serial clock pin sck of the serial peripheral interface 1 (spi1). 1.2.2.24 ph1 / kwh1 / mosi1 ?port h i/o pin 1 ph1 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as master output (during master mode) or slave input pin (during slave mode) mosi of the serial peripheral interface 1 (spi1). chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 34 freescale semiconductor 1.2.2.25 ph0 / kwh0 / miso1 ?port h i/o pin 0 ph0 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as master input (during master mode) or slave output (during slave mode) pin miso of the serial peripheral interface 1 (spi1). 1.2.2.26 pj7 / kwj7 / txcan4 / scl ?port j i/o pin 7 pj7 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as the transmit pin txcan for the scalable controller area network controller 4 (can4) or the serial clock pin scl of the iic module. 1.2.2.27 pj6 / kwj6 / rxcan4 / sda ?port j i/o pin 6 pj6 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as the receive pin rxcan for the scalable controller area network controller 4 (can4) or the serial data pin sda of the iic module. 1.2.2.28 pj[1:0] / kwj[1:0] ?port j i/o pins [1:0] pj1 and pj0 are general purpose input or output pins. they can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. 1.2.2.29 pk7 / ecs / romctl ?port k i/o pin 7 pk7 is a general purpose input or output pin. during mcu expanded modes of operation, this pin is used as the emulation chip select output ( ecs). during mcu expanded modes of operation, this pin is used to enable the flash eeprom memory in the memory map (romctl). at the rising edge of reset, the state of this pin is latched to the romon bit. chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 35 for all other modes the reset state of the romon bit is as follows: special single: romctl = 1 normal single: romctl = 1 emulation expanded wide: romctl = 0 emulation expanded narrow: romctl = 0 special test: romctl = 0 peripheral test: romctl = 1 1.2.2.30 pk[5:0] / xaddr[19:14] ?port k i/o pins [5:0] pk5-pk0 are general purpose input or output pins. in mcu expanded modes of operation, these pins provide the expanded address xaddr[19:14] for the external bus. 1.2.2.31 pm7 / txcan4 ?port m i/o pin 7 pm7 is a general purpose input or output pin. it can be con?ured as the transmit pin txcan of the scalable controller area network controllers 4 (can4). 1.2.2.32 pm6 / rxcan4 ?port m i/o pin 6 pm6 is a general purpose input or output pin. it can be con?ured as the receive pin rxcan of the scalable controller area network controllers 4 (can4). 1.2.2.33 pm5 / txcan0 / txcan4 / sck0 ?port m i/o pin 5 pm5 is a general purpose input or output pin. it can be con?ured as the transmit pin txcan of the scalable controller area network controllers 0 or 4 (can0 or can4). it can be con?ured as the serial clock pin sck of the serial peripheral interface 0 (spi0). 1.2.2.34 pm4 / rxcan0 / rxcan4/ mosi0 ?port m i/o pin 4 pm4 is a general purpose input or output pin. it can be con?ured as the receive pin rxcan of the scalable controller area network controllers 0 or 4 (can0 or can4). it can be con?ured as the master output (during master mode) or slave input pin (during slave mode) mosi for the serial peripheral interface 0 (spi0). 1.2.2.35 pm3 / txcan0 / ss0 ?port m i/o pin 3 pm3 is a general purpose input or output pin. it can be con?ured as the transmit pin txcan of the scalable controller area network controller 0 (can0). it can be con?ured as the slave select pin ss of the serial peripheral interface 0 (spi0). chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 36 freescale semiconductor 1.2.2.36 pm2 / rxcan0 / miso0 ?port m i/o pin 2 pm2 is a general purpose input or output pin. it can be con?ured as the receive pin rxcan of the scalable controller area network controller 0 ( can0). it can be con?ured as the master input (during master mode) or slave output pin (during slave mode) miso for the serial peripheral interface 0 (spi0). 1.2.2.37 pm1 / txcan0 ?port m i/o pin 1 pm1 is a general purpose input or output pin. it can be con?ured as the transmit pin txcan of the scalable controller area network controller 0 (can0). 1.2.2.38 pm0 / rxcan0 ?port m i/o pin 0 pm0 is a general purpose input or output pin. it can be con?ured as the receive pin rxcan of the scalable controller area network controller 0 (can0). 1.2.2.39 pp7 / kwp7 / pwm7 / sck2 ?port p i/o pin 7 pp7 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as pulse width modulator (pwm) channel 7 output. it can be con?ured as serial clock pin sck of the serial peripheral interface 2 (spi2). 1.2.2.40 pp6 / kwp6 / pwm6 / ss2 ?port p i/o pin 6 pp6 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as pulse width modulator (pwm) channel 6 output. it can be con?ured as slave select pin ss of the serial peripheral interface 2 (spi2). 1.2.2.41 pp5 / kwp5 / pwm5 / mosi2 ?port p i/o pin 5 pp5 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as pulse width modulator (pwm) channel 5 output. it can be con?ured as master output (during master mode) or slave input pin (during slave mode) mosi of the serial peripheral interface 2 (spi2). 1.2.2.42 pp4 / kwp4 / pwm4 / miso2 ?port p i/o pin 4 pp4 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as pulse width modulator (pwm) channel 4 output. it can be con?ured as master input (during master mode) or slave output (during slave mode) pin miso of the serial peripheral interface 2 (spi2). 1.2.2.43 pp3 / kwp3 / pwm3 / ss1 ?port p i/o pin 3 pp3 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as pulse width modulator (pwm) channel 3 output. it can be con?ured as slave select pin ss of the serial peripheral interface 1 (spi1). chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 37 1.2.2.44 pp2 / kwp2 / pwm2 / sck1 ?port p i/o pin 2 pp2 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as pulse width modulator (pwm) channel 2 output. it can be con?ured as serial clock pin sck of the serial peripheral interface 1 (spi1). 1.2.2.45 pp1 / kwp1 / pwm1 / mosi1 ?port p i/o pin 1 pp1 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as pulse width modulator (pwm) channel 1 output. it can be con?ured as master output (during master mode) or slave input pin (during slave mode) mosi of the serial peripheral interface 1 (spi1). 1.2.2.46 pp0 / kwp0 / pwm0 / miso1 ?port p i/o pin 0 pp0 is a general purpose input or output pin. it can be con?ured to generate an interrupt causing the mcu to exit stop or wait mode. it can be con?ured as pulse width modulator (pwm) channel 0 output. it can be con?ured as master input (during master mode) or slave output (during slave mode) pin miso of the serial peripheral interface 1 (spi1). 1.2.2.47 ps7 / ss0 ?port s i/o pin 7 ps6 is a general purpose input or output pin. it can be con?ured as the slave select pin ss of the serial peripheral interface 0 (spi0). 1.2.2.48 ps6 / sck0 ?port s i/o pin 6 ps6 is a general purpose input or output pin. it can be con?ured as the serial clock pin sck of the serial peripheral interface 0 (spi0). 1.2.2.49 ps5 / mosi0 ?port s i/o pin 5 ps5 is a general purpose input or output pin. it can be con?ured as master output (during master mode) or slave input pin (during slave mode) mosi of the serial peripheral interface 0 (spi0). 1.2.2.50 ps4 / miso0 ?port s i/o pin 4 ps4 is a general purpose input or output pin. it can be con?ured as master input (during master mode) or slave output pin (during slave mode) mosi of the serial peripheral interface 0 (spi0). 1.2.2.51 ps3 / txd1 ?port s i/o pin 3 ps3 is a general purpose input or output pin. it can be con?ured as the transmit pin txd of serial communication interface 1 (sci1). chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 38 freescale semiconductor 1.2.2.52 ps2 / rxd1 ?port s i/o pin 2 ps2 is a general purpose input or output pin. it can be con?ured as the receive pin rxd of serial communication interface 1 (sci1). 1.2.2.53 ps1 / txd0 ?port s i/o pin 1 ps1 is a general purpose input or output pin. it can be con?ured as the transmit pin txd of serial communication interface 0 (sci0). 1.2.2.54 ps0 / rxd0 ?port s i/o pin 0 ps0 is a general purpose input or output pin. it can be con?ured as the receive pin rxd of serial communication interface 0 (sci0). 1.2.2.55 pt[7:0] / ioc[7:0] ?port t i/o pins [7:0] pt7-pt0 are general purpose input or output pins. they can be con?ured as input capture or output compare pins ioc7-ioc0 of the timer (tim). 1.2.3 power supply pins mc9s12kg128 power and ground pins are described below. note all vss pins must be connected together in the application. 1.2.3.1 vddx,vssx ?power supply pins for i/o drivers external power and ground for i/o drivers. because fast signal transitions place high, short-duration current demands on the power supply, use bypass capacitors with high-frequency characteristics and place them as close to the mcu as possible. bypass requirements depend on how heavily the mcu pins are loaded. 1.2.3.2 vddr, vssr power supply pins for i/o drivers & for internal voltage regulator external power and ground for i/o drivers and input to the internal voltage regulator. because fast signal transitions place high, short-duration current demands on the power supply, use bypass capacitors with high-frequency characteristics and place them as close to the mcu as possible. bypass requirements depend on how heavily the mcu pins are loaded. 1.2.3.3 vdd1, vdd2, vss1, vss2 ?power supply pins for internal logic power is supplied to the mcu through vdd and vss. because fast signal transitions place high, short-duration current demands on the power supply, use bypass capacitors with high-frequency characteristics and place them as close to the mcu as possible. this 2.5v supply is derived from the chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 39 internal voltage regulator. there is no static load on those pins allowed. the internal voltage regulator is turned off, if vregen is tied to ground. note no load allowed except for bypass capacitors. 1.2.3.4 vdda, vssa ?power supply pins for atd and vreg vdda, vssa are the power supply and ground input pins for the voltage regulator and the analog to digital converter. it also provides the reference for the internal voltage regulator. this allows the supply voltage to the atd and the reference voltage to be bypassed independently. 1.2.3.5 vrh, vrl ?atd reference voltage input pins vrh and vrl are the reference voltage input pins for the analog to digital converter. 1.2.3.6 vddpll, vsspll ?power supply pins for pll provides operating voltage and ground for the oscillator and the phased-locked loop. this allows the supply voltage to the oscillator and pll to be bypassed independently. this 2.5v voltage is generated by the internal voltage regulator. note no load allowed except for bypass capacitors. chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 40 freescale semiconductor 1.3 memory map and register de?ition 1.3.1 device memory map table 1-5 shows the device register map of the mc9s12kg128 after reset. table 1-5. mc9s12kt256 device memory map address module size 0x0000?x0017 core (ports a, b, e, modes, inits, test) 24 0x0018 reserved 1 0x0019 voltage regulator (vreg) 1 0x001a?x001b device id register (partid) 2 0x001c?x001f core (memsiz, irq, hprio) 4 0x0020?x002f core (dbg) 16 0x0030?x0033 core (ppage, port k) 4 0x0034?x003f clock and reset generator (pll, rti, cop) 12 0x0040?x006f standard timer 16-bit 8 channels (tim) 48 0x0070?x007f reserved 16 0x0080?x00af analog to digital converter 10-bit 16 channels (atd) 48 0x00b0?x00c7 reserved 24 0x00c8?x00cf serial communications interface 0 (sci0) 8 0x00d0?x00d7 serial communications interface 1 (sci1) 8 0x00d8?x00df serial peripheral interface 0 (spi0) 8 0x00e0?x00e7 inter integrated circuit bus (iic) 8 0x00e8?x00ef reserved 8 0x00f0?x00f7 serial peripheral interface 1 (spi1) 8 0x00f8?x00ff serial peripheral interface 2 (spi2) 8 0x0100?x010f flash control register 16 0x0110- 0x011b eeprom control register 12 0x011c?x013f reserved 36 0x0140?x017f scalable controller area network 0 (can0) 64 0x0180?x023f reserved 192 0x0240?x027f port integration module (pim) 64 0x0280?x02bf scalable controller area network 4 (can4) 64 0x02c0?x02e7 pulse width modulator 8-bit 8 channels (pwm) 40 0x02e8?x03ff reserved 280 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 41 figure 1-9 illustrates the full user con?urable device memory map of mc9s12kg128. figure 1-9. mc9s12kg128 memory map the ?ure shows a useful map, which is not the map out of reset. after reset the map is: 0x0000?x03ff: register space 0x0000?x1fff: 8k ram (1k ram hidden behind register space) 0x0000?x07ff: 2k eeprom (not visible) 0x0000 0 xffff 0 xc000 0x8000 0x4000 0x0400 0x0800 0x1000 0x2000 0xff00 ext normal single chip expanded special single chip vectors vectors vectors 0xff00 0xffff bdm (if active) 0xc000 0xffff 16k fixed flash eeprom 2k, 4k, 8k or 16k protected boot sector 0x8000 0xbfff 16k page window eight * 16k flash eeprom pages 0x4000 0x7fff 16k fixed flash eeprom 0.5k, 1k, 2k or 4k protected sector 0x2000 0x3fff 8k bytes ram mappable to any 8k boundary 0x0800 0x0fff 2k bytes eeprom mappable to any 2k boundary 0x0000 0x03ff 1k register space mappable to any 2k boundary chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 42 freescale semiconductor figure 1-10 illustrates the full user con?urable device memory map of mc9s12kl64 and mc9s12kc64. figure 1-10. mc9s12kl(c)64 memory map the ?ure shows a useful map, which is not the map out of reset. after reset the map is: 0x0000?x03ff: register space 0x0000?x0fff: 4k ram (1k ram hidden behind register space) 0x0000?x03ff: 1k eeprom (not visible) 0x0000 0 xffff 0 xc000 0x8000 0x4000 0x0400 0x0800 0x1000 0x3000 0xff00 ext normal single chip expanded special single chip vectors vectors vectors 0xff00 0xffff bdm (if active) 0xc000 0xffff 16k fixed flash eeprom 2k, 4k, 8k or 16k protected boot sector 0x8000 0xbfff 16k page window four * 16k flash eeprom pages 0x4000 0x7fff 16k fixed flash eeprom 0.5k, 1k, 2k or 4k protected sector 0x3000 0x3fff 4k bytes ram mappable to any 4k boundary 0x0800 0x0fff 1k bytes eeprom mappable to any 2k boundary 0x0000 0x03ff 1k register space mappable to any 2k boundary (1k mapped two times in 2k space) chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 43 figure 1-11 illustrates the full user con?urable device memory map of mc9s12kl32. figure 1-11. mc9s12kl32 memory map the ?ure shows a useful map, which is not the map out of reset. after reset the map is: 0x0000?x03ff: register space 0x0000?x07ff: 2k ram (1k ram hidden behind register space) 0x0000?x03ff: 1k eeprom (not visible) 0x0000 0 xffff 0x8000 0x4000 0x0400 0x0800 0x1000 0x3800 0xff00 ext normal single chip expanded special single chip vectors vectors vectors 0xff00 0xffff bdm (if active) 0xffff 32k fixed flash eeprom 2k, 4k, 8k or 16k protected boot sector 0x8000 0x3800 0x3fff 2k bytes ram mappable to any 2k boundary 0x0800 0x0fff 1k bytes eeprom mappable to any 2k boundary 0x0000 0x03ff 1k register space mappable to any 2k boundary (1k mapped two times in 2k space) chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 44 freescale semiconductor 1.3.2 detailed register map the following tables show the detailed register map of the mc9s12kg128. 0x0000?x000f mebi map 1 of 3 (hcs12 multiplexed external bus interface) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0000 porta r bit 7 6 5 4 3 2 1 bit 0 w 0x0001 portb r bit 7 6 5 4 3 2 1 bit 0 w 0x0002 ddra r bit 7 6 5 4 3 2 1 bit 0 w 0x0003 ddrb r bit 7 6 5 4 3 2 1 bit 0 w 0x0004 reserved r00000000 w 0x0005 reserved r00000000 w 0x0006 reserved r00000000 w 0x0007 reserved r00000000 w 0x0008 porte r bit 7 6 5 4 3 2 bit 1 bit 0 w 0x0009 ddre r bit 7 6 5 4 3 bit 2 00 w 0x000a pear r noacce 0 pipoe neclk lstre rdwe 00 w 0x000b mode r modc modb moda 0 ivis 0 emk eme w 0x000c pucr r pupke 00 pupee 00 pupbe pupae w 0x000d rdriv r rdpk 00 rdpe 00 rdpb rdpa w 0x000e ebictl r0000000 estr w 0x000f reserved r00000000 w chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 45 0x0010?x0014 mmc map 1 of 4 (hcs12 module mapping control) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0010 initrm r ram15 ram14 ram13 ram12 ram11 00 ramhal w 0x0011 initrg r0 reg14 reg13 reg12 reg11 000 w 0x0012 initee r ee15 ee14 ee13 ee12 ee11 00 eeon w 0x0013 misc r0 0 0 0 exstr1 exstr0 romhm romon w 0x0014 reserved r00000000 w 0x0015?x0016 int map 1 of 2 (hcs12 interrupt) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0015 itcr r0 0 0 wrint adr3 adr2 adr1 adr0 w 0x0016 itest r inte intc inta int8 int6 int4 int2 int0 w 0x0017?x0017 mmc map 2 of 4 (hcs12 module mapping control) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0017 reserved r00000000 w 0x0018?x0018 miscellaneous peripherals (device guide) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0018 reserved r00000000 w 0x0019?x0019 vreg3v3 (voltage regulator) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0019 vregctrl r00000lvds lvie lvif w 0x001a?x001b miscellaneous peripherals (device guide) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x001a partidh r id15 id14 id13 id12 id11 id10 id9 id8 w 0x001b partidl r id7 id6 id5 id4 id3 id2 id1 id0 w chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 46 freescale semiconductor 0x001c?x001d mmc map 3 of 4 (hcs12 module mapping control, device guide) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x001c memsiz0 r reg_sw0 0 eep_sw1 eep_sw0 0 ram_sw2 ram_sw1 ram_sw0 w 0x001d memsiz1 r rom_sw1 rom_sw0 0 0 0 0 pag_sw1 pag_sw0 w 0x001e?x001e mebi map 2 of 3 (hcs12 multiplexed external bus interface) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x001e intcr r irqe irqen 000000 w 0x001f?x001f int map 2 of 2 (hcs12 interrupt) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x001f hprio r psel7 psel6 psel5 psel4 psel3 psel2 psel1 0 w 0x0020?x002f dbg map 1 of 1 (hcs12 debug) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0020 dbgc1 r dbgen arm trgsel begin dbgbrk 0 capmod ? 0x0021 dbgsc r af bf cf 0 trg ? 0x0022 dbgtbh r bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 ? 0x0023 dbgtbl r bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 ? 0x0024 dbgcnt r tbf 0 cnt ? 0x0025 dbgccx r pagsel extcmp ? 0x0026 dbgcch r bit 15 14 13 12 11 10 9 bit 8 ? 0x0027 dbgccl r bit 7 6 5 4 3 2 1 bit 0 ? 0x0028 dbgc2 r bkaben full bdm tagab bkcen tagc rwcen rwc bkpct0 w 0x0029 dbgc3 r bkambh bkambl bkbmbh bkbmbl rwaen rwa rwben rwb bkpct1 w 0x002a dbgcax r pagsel extcmp bkp0x w 0x002b dbgcah r bit 15 14 13 12 11 10 9 bit 8 bkp0h w chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 47 0x002c dbgcal r bit 7 6 5 4 3 2 1 bit 0 bkp0l w 0x002d dbgcbx r pagsel extcmp bkp1x w 0x002e dbgcbh r bit 15 14 13 12 11 10 9 bit 8 bkp1h w 0x002f dbgcbl r bit 7 6 5 4 3 2 1 bit 0 bkp1l w 0x0030?x0031 mmc map 4 of 4 (hcs12 module mapping control) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0030 ppage r0 0 pix5 pix4 pix3 pix2 pix1 pix0 w 0x0031 reserved r00000000 w 0x0032?x0033 mebi map 3 of 3 (hcs12 multiplexed external bus interface) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0032 portk r bit 7 6 5 4 3 2 1 bit 0 w 0x0033 ddrk r bit 7 6 5 4 3 2 1 bit 0 w 0x0034?x003f crg (clock and reset generator) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0034 synr r0 0 syn5 syn4 syn3 syn2 syn1 syn0 w 0x0035 refdv r0 0 0 0 refdv3 refdv2 refdv1 refdv0 w 0x0036 ctflg test only r tout7 tout6 tout5 tout4 tout3 tout2 tout1 tout0 w 0x0037 crgflg r rtif prof 0 lockif lock track scmif scm w 0x0038 crgint r rtie 00 lockie 00 scmie 0 w 0x0039 clksel r pllsel pstp syswai roawai pllwai cwai rtiwai copwai w 0x003a pllctl r cme pllon auto acq 0 pre pce scme w 0x003b rtictl r0 rtr6 rtr5 rtr4 rtr3 rtr2 rtr1 rtr0 w 0x0020?x002f dbg map 1 of 1 (hcs12 debug) (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 48 freescale semiconductor 0x003c copctl r wcop rsbck 000 cr2 cr1 cr0 w 0x003d forbyp test only r rtibyp copbyp 0 pllbyp 00 fcm 0 w 0x003e ctctl test only r tctl7 tctl6 tctl5 tctl4 tclt3 tctl2 tctl1 tctl0 w 0x003f armcop r00000000 w bit 7 6 5 4 3 2 1 bit 0 0x0040?x006ftim (timer 16 bit 8 channels) (sheet 1 of 3) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0040 tios r ios7 ios6 ios5 ios4 ios3 ios2 ios1 ios0 w 0x0041 cforc r00000000 w foc7 foc6 foc5 foc4 foc3 foc2 foc1 foc0 0x0042 oc7m r oc7m7 oc7m6 oc7m5 oc7m4 oc7m3 oc7m2 oc7m1 oc7m0 w 0x0043 oc7d r oc7d7 oc7d6 oc7d5 oc7d4 oc7d3 oc7d2 oc7d1 oc7d0 w 0x0044 tcnt (hi) r bit 15 14 13 12 11 10 9 bit 8 w 0x0045 tcnt (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x0046 tscr1 r ten tswai tsfrz tffca 0000 w 0x0047 ttov r tov7 tov6 tov5 tov4 tov3 tov2 tov1 tov0 w 0x0048 tctl1 r om7 ol7 om6 ol6 om5 ol5 om4 ol4 w 0x0049 tctl2 r om3 ol3 om2 ol2 om1 ol1 om0 ol0 w 0x004a tctl3 r edg7b edg7a edg6b edg6a edg5b edg5a edg4b edg4a w 0x004b tctl4 r edg3b edg3a edg2b edg2a edg1b edg1a edg0b edg0a w 0x004c tie r c7i c6i c5i c4i c3i c2i c1i c0i w 0x004d tscr2 r toi 000 tcre pr2 pr1 pr0 w 0x004e tflg1 r c7f c6f c5f c4f c3f c2f c1f c0f w 0x004f tflg2 r tof 0000000 w 0x0034?x003f crg (clock and reset generator) (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 49 0x0050 tc0 (hi) r bit 15 14 13 12 11 10 9 bit 8 w 0x0051 tc0 (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x0052 tc1 (hi) r bit 15 14 13 12 11 10 9 bit 8 w 0x0053 tc1 (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x0054 tc2 (hi) r bit 15 14 13 12 11 10 9 bit 8 w 0x0055 tc2 (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x0056 tc3 (hi) r bit 15 14 13 12 11 10 9 bit 8 w 0x0057 tc3 (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x0058 tc4 (hi) r bit 15 14 13 12 11 10 9 bit 8 w 0x0059 tc4 (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x005a tc5 (hi) r bit 15 14 13 12 11 10 9 bit 8 w 0x005b tc5 (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x005c tc6 (hi) r bit 15 14 13 12 11 10 9 bit 8 w 0x005d tc6 (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x005e tc7 (hi) r bit 15 14 13 12 11 10 9 bit 8 w 0x005f tc7 (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x0060 pactl r0 paen pamod pedge clk1 clk0 paovi pai w 0x0061 paflg r000000 paovf paif w 0x0062 pacnt (hi) r bit 7 6 5 4 3 2 1 bit 0 w 0x0063 pacnt (lo) r bit 7 6 5 4 3 2 1 bit 0 w 0x0064 reserved r00000000 w 0x0065 reserved r00000000 w 0x0066 reserved r00000000 w 0x0040?x006ftim (timer 16 bit 8 channels) (sheet 2 of 3) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 50 freescale semiconductor 0x0067 reserved r00000000 w 0x0068 reserved r00000000 w 0x0069 reserved r00000000 w 0x006a reserved r00000000 w 0x006b reserved r00000000 w 0x006c reserved r00000000 w 0x006d reserved r00000000 w 0x006e reserved r00000000 w 0x006f reserved r00000000 w 0x0070?x007freserved space address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0070 0x007f reserved r00000000 w 0x0080?x00af atd (analog to digital converter 10 bit 16 channel) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0080 atdctl0 r0 0 0 0 wrap3 wrap2 wrap1 wrap0 w 0x0081 atdctl1 r e trigsel 000 etrigch3 etrigch2 etrigch1 etrigch0 w 0x0082 atdctl2 r adpu affc awai etrigle etrigp etrig ascie ascif w 0x0083 atdctl3 r0 s8c s4c s2c s1c fifo frz1 frz0 w 0x0084 atdctl4 r sres8 smp1 smp0 prs4 prs3 prs2 prs1 prs0 w 0x0085 atdctl5 r djm dsgn scan mult 0 cc cb ca w 0x0086 atdstat0 r scf 0 etorf fifor 0 cc2 cc1 cc0 w 0x0087 reserved r00000000 w 0x0040?x006ftim (timer 16 bit 8 channels) (sheet 3 of 3) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 51 0x0088 atdtest0 r00000000 w 0x0089 atdtest1 r00000 0 0 sc w 0x008a atdstat0 r ccf15 ccf14 ccf13 ccf12 ccf11 ccf10 ccf9 ccf8 w 0x008b atdstat1 r ccf7 ccf6 ccf5 ccf4 ccf3 ccf2 ccf1 ccf0 w 0x008c atddien1 r ien15 ien14 ien13 ien12 ien11 ien10 ien9 ien8 w 0x008d atddien0 r ien7 ien6 ien5 ien4 ien3 ien2 ien1 ien0 w 0x008e portad1 r ptad15 ptad14 ptad13 ptad12 ptad11 ptad10 ptad9 ptad8 w 0x008f portad0 r ptad7 ptad6 ptad5 ptad4 ptad3 ptad2 ptad1 ptad0 w 0x0090 atddr0h r bit 15 14 13 12 11 10 9 bit 8 w 0x0091 atddr0l r bit 7 bit 6 0 0 0 0 0 0 w 0x0092 atddr1h r bit 15 14 13 12 11 10 9 bit 8 w 0x0093 atddr1l r bit 7 bit 6 0 0 0 0 0 0 w 0x0094 atddr2h r bit 15 14 13 12 11 10 9 bit 8 w 0x0095 atddr2l r bit 7 bit 6 0 0 0 0 0 0 w 0x0096 atddr3h r bit 15 14 13 12 11 10 9 bit 8 w 0x0097 atddr3l r bit 7 bit 6 0 0 0 0 0 0 w 0x0098 atddr4h r bit 15 14 13 12 11 10 9 bit 8 w 0x0099 atddr4l r bit 7 bit 6 0 0 0 0 0 0 w 0x009a atddr5h r bit 15 14 13 12 11 10 9 bit 8 w 0x009b atddr5l r bit 7 bit 6 0 0 0 0 0 0 w 0x009c atddr6h r bit 15 14 13 12 11 10 9 bit 8 w 0x009d atddr6l r bit 7 bit 6 0 0 0 0 0 0 w 0x009e atddr7h r bit 15 14 13 12 11 10 9 bit 8 w 0x0080?x00af atd (analog to digital converter 10 bit 16 channel) (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 52 freescale semiconductor 0x009f atddr7l r bit 7 bit 6 0 0 0 0 0 0 w 0x00a0 atddr8h r bit 15 14 13 12 11 10 9 bit 8 w 0x00a1 atddr8l r bit 7 bit 6 0 0 0 0 0 0 w 0x00a2 atddr9h r bit 15 14 13 12 11 10 9 bit 8 w 0x00a3 atddr9l r bit 7 bit 6 0 0 0 0 0 0 w 0x00a4 atddr10h r bit 15 14 13 12 11 10 9 bit 8 w 0x00a5 atddr10l r bit 7 bit 6 0 0 0 0 0 0 w 0x00a6 atddr11h r bit 15 14 13 12 11 10 9 bit 8 w 0x00a7 atddr11l r bit 7 bit 6 0 0 0 0 0 0 w 0x00a8 atddr12h r bit 15 14 13 12 11 10 9 bit 8 w 0x00a9 atddr12l r bit 7 bit 6 0 0 0 0 0 0 w 0x00aa atddr13h r bit 15 14 13 12 11 10 9 bit 8 w 0x00ab atddr13l r bit 7 bit 6 0 0 0 0 0 0 w 0x00ac atddr14h r bit 15 14 13 12 11 10 9 bit 8 w 0x00ad atddr14l r bit 7 bit 6 0 0 0 0 0 0 w 0x00ae atddr15h r bit 15 14 13 12 11 10 9 bit 8 w 0x00af atddr15l r bit 7 bit 6 0 0 0 0 0 0 w 0x00b0?x00c7 reserved space address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00b0 0x00c7 reserved r00000000 w 0x0080?x00af atd (analog to digital converter 10 bit 16 channel) (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 53 0x00c8?x00cf sci0 (asynchronous serial interface) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00c8 sci0bdh r0 0 0 sbr12 sbr11 sbr10 sbr9 sbr8 w 0x00c9 sci0bdl r sbr7 sbr6 sbr5 sbr4 sbr3 sbr2 sbr1 sbr0 w 0x00ca sci0cr1 r loops sciswai rsrc m wake ilt pe pt w 0x00cb sci0cr2 r tie tcie rie ilie te re rwu sbk w 0x00cc sci0sr1 r tdre tc rdrf idle or nf fe pf w 0x00cd sci0sr2 r00000 brk13 txdir raf w 0x00ce sci0drh rr8 t8 000000 w 0x00cf sci0drl rr7r6r5r4r3r2r1r0 wt7t6t5t4t3t2t1t0 0x00d0?x00d7 sci1 (asynchronous serial interface) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00d0 sci1bdh r0 0 0 sbr12 sbr11 sbr10 sbr9 sbr8 w 0x00d1 sci1bdl r sbr7 sbr6 sbr5 sbr4 sbr3 sbr2 sbr1 sbr0 w 0x00d2 sci1cr1 r loops sciswai rsrc m wake ilt pe pt w 0x00d3 sci1cr2 r tie tcie rie ilie te re rwu sbk w 0x00d4 sci1sr1 r tdre tc rdrf idle or nf fe pf w 0x00d5 sci1sr2 r00000 brk13 txdir raf w 0x00d6 sci1drh rr8 t8 000000 w 0x00d7 sci1drl rr7r6r5r4r3r2r1r0 wt7t6t5t4t3t2t1t0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 54 freescale semiconductor 0x00d8?x00df spi0 (serial peripheral interface) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00d8 spi0cr1 r spie spe sptie mstr cpol cpha ssoe lsbfe w 0x00d9 spi0cr2 r0 0 0 modfen bidiroe 0 spiswai spc0 w 0x00da spi0br r0 sppr2 sppr1 sppr0 0 spr2 spr1 spr0 w 0x00db spi0sr r spif 0 sptef modf 0 0 0 0 w 0x00dc reserved r00000000 w 0x00dd spi0dr r bit 7 6 5 4 3 2 1 bit 0 w 0x00de reserved r00000000 w 0x00df reserved r00000000 w 0x00e0?x00e7 iic (inter ic bus) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00e0 ibad r adr7 adr6 adr5 adr4 adr3 adr2 adr1 0 w 0x00e1 ibfd r ibc7 ibc6 ibc5 ibc4 ibc3 ibc2 ibc1 ibc0 w 0x00e2 ibcr r iben ibie ms/ sl tx/ rx txak 00 ibswai w rsta 0x00e3 ibsr r tcf iaas ibb ibal 0srw ibif rxak w 0x00e4 ibdr r d7 d6 d5 d4 d3 d2 d1 d 0 w 0x00e5 reserved r0 0 0 0 0 0 0 0 w 0x00e6 reserved r00000000 w 0x00e7 reserved r00000000 w 0x00e8?x00ef reserved space address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00e8 0x00ef reserved r00000000 w chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 55 0x00f0?x00f7 spi1 (serial peripheral interface) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00f0 spi1cr1 r spie spe sptie mstr cpol cpha ssoe lsbfe w 0x00f1 spi1cr2 r0 0 0 modfen bidiroe 0 spiswai spc0 w 0x00f2 spi1br r0 sppr2 sppr1 sppr0 0 spr2 spr1 spr0 w 0x00f3 spi1sr r spif 0 sptef modf 0 0 0 0 w 0x00f4 reserved r00000000 w 0x00f5 spi1dr r bit 7 6 5 4 3 2 1 bit 0 w 0x00f6 reserved r00000000 w 0x00f7 reserved r00000000 w 0x00f8?x00ff spi2 (serial peripheral interface) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00f8 spi2cr1 r spie spe sptie mstr cpol cpha ssoe lsbfe w 0x00f9 spi2cr2 r0 0 0 modfen bidiroe 0 spiswai spc0 w 0x00fa spi2br r0 sppr2 sppr1 sppr0 0 spr2 spr1 spr0 w 0x00fb spi2sr r spif 0 sptef modf 0 0 0 0 w 0x00fc reserved r00000000 w 0x00fd spi2dr r bit 7 6 5 4 3 2 1 bit 0 w 0x00fe reserved r00000000 w 0x00ff reserved r00000000 w 0x0100?x010f flash control register address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0100 fclkdiv r fdivld prdiv8 fdiv5 fdiv4 fdiv3 fdiv2 fdiv1 fdiv0 w 0x0101 fsec r keyen rnv5 rnv4 rnv3 rnv2 sec w chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 56 freescale semiconductor 0x0102 ftstmod r0 0 0 0 fdfd 000 w 0x0103 fcnfg r cbeie ccie keyacc 0 dfdie 000 w 0x0104 fprot r fpopen rnv6 fphdis fphs fpldis fpls w 0x0105 fstat r cbeif ccif pviol accerr dfdif blank 0 0 w 0x0106 fcmd r0 cmdb w 0x0107 reserved r00000000 w 0x0108 faddrhi r faddrhi w 0x0109 faddrlo r faddrlo w 0x010a fdatahi r fdatahi w 0x010b fdatalo r fdatalo w 0x010c reserved r00000000 w 0x010d reserved r00000000 w 0x010e reserved r00000000 w 0x010f reserved r00000000 w 0x0110?x011b eeprom control register address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0110 eclkdiv r edivld prdiv8 ediv5 ediv4 ediv3 ediv2 ediv1 ediv0 w 0x0111 reserved r00000000 w 0x0112 reserved for factory test r00000000 w 0x0113 ecnfg r cbeie ccie 000000 w 0x0114 eprot r epopen nv6 nv5 nv4 epdis ep2 ep1 ep0 w 0x0115 estat r cbeif ccif pviol accerr 0 blank 00 w 0x0100?x010f flash control register (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 57 0x0116 ecmd r0 cmdb6 cmdb5 00 cmdb2 0 cmdb0 w 0x0117 reserved for factory test r00000000 w 0x0118 eaddrhi r00000 10 9 bit 8 w 0x0119 eaddrlo r bit 7 6 5 4 3 2 1 bit 0 w 0x011a edatahi r bit 15 14 13 12 11 10 9 bit 8 w 0x011b edatalo r bit 7 6 5 4 3 2 1 bit 0 w 0x011c?x013f reserved space address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x011c 0x013f reserved r00000000 w 0x0140?x017f can0 (mscan) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0140 can0ctl0 r rxfrm rxact cswai synch time wupe slprq initrq w 0x0141 can0ctl1 r cane clksrc loopb listen 0 wupm slpak initak w 0x0142 can0btr0 r sjw1 sjw0 brp5 brp4 brp3 brp2 brp1 brp0 w 0x0143 can0btr1 r samp tseg22 tseg21 tseg20 tseg13 tseg12 tseg11 tseg10 w 0x0144 can0rflg r wupif cscif rstat1 rstat0 tstat1 tstat0 ovrif rxf w 0x0145 can0rier r wupie cscie rstate1 rstate0 tstate1 tstate0 ovrie rxfie w 0x0146 can0tflg r00000 txe2 txe1 txe0 w 0x0147 can0tier r00000 txeie2 txeie1 txeie0 w 0x0148 can0tarq r00000 abtrq2 abtrq1 abtrq0 w 0x0149 can0taak r 0 0 0 0 0 abtak2 abtak1 abtak0 w 0x014a can0tbsel r00000 tx2 tx1 tx0 w 0x0110?x011b eeprom control register (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 58 freescale semiconductor 0x014b can0idac r0 0 idam1 idam0 0 idhit2 idhit1 idhit0 w 0x014c reserved r00000000 w 0x014d reserved r00000000 w 0x014e can0rxerr r rxerr7 rxerr6 rxerr5 rxerr4 rxerr3 rxerr2 rxerr1 rxerr0 w 0x014f can0txerr r txerr7 txerr6 txerr5 txerr4 txerr3 txerr2 txerr1 txerr0 w 0x0150 0x0153 can0idar0 can0idar3 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x0154 0x0157 can0idmr0 can0idmr3 r am7 am6 am5 am4 am3 am2 am1 am0 w 0x0158 0x015b can0idar4 can0idar7 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x015c 0x015f can0idmr4 can0idmr7 r am7 am6 am5 am4 am3 am2 am1 am0 w 0x0160 0x016f can0rxfg r foreground receive buffer (see table 1-6 ) w 0x0170 0x017f can0txfg r foreground transmit buffer (see table 1-6 ) w table 1-6. detailed mscan foreground receive and transmit buffer layout address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x00 extended id r id28 id27 id26 id25 id24 id23 id22 id21 standard id r id10 id9 id8 id7 id6 id5 id4 id3 canxridr0 w 0x01 extended id r id20 id19 id18 srr=1 ide=1 id17 id16 id15 standard id r id2 id1 id0 rtr ide=0 canxridr1 w 0x02 extended id r id14 id13 id12 id11 id10 id9 id8 id7 standard id r canxridr2 w 0x03 extended id r id6 id5 id4 id3 id2 id1 id0 rtr standard id r canxridr3 w 0x04 0x0b canxrdsr0 canxrdsr7 r db7 db6 db5 db4 db3 db2 db1 db0 w 0x0c canrxdlr r dlc3 dlc2 dlc1 dlc0 w 0x0d reserved r w 0x0e canxrtsrh r tsr15 tsr14 tsr13 tsr12 tsr11 tsr10 tsr9 tsr8 w 0x0140?x017f can0 (mscan) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 59 0x0f canxrtsrl r tsr7 tsr6 tsr5 tsr4 tsr3 tsr2 tsr1 tsr0 w 0x10 extended id r id28 id27 id26 id25 id24 id23 id22 id21 canxtidr0 w standard id r id10 id9 id8 id7 id6 id5 id4 id3 w 0x10 extended id r id20 id19 id18 srr=1 ide=1 id17 id16 id15 canxtidr1 w standard id r id2 id1 id0 rtr ide=0 w 0x12 extended id r id14 id13 id12 id11 id10 id9 id8 id7 canxtidr2 w standard id r w 0x13 extended id r id6 id5 id4 id3 id2 id1 id0 rtr canxtidr3 w standard id r w 0x14 0x1b canxtdsr0 canxtdsr7 r db7 db6 db5 db4 db3 db2 db1 db0 w 0x1c canxtdlr r dlc3 dlc2 dlc1 dlc0 w 0x1d conxttbpr r prio7 prio6 prio5 prio4 prio3 prio2 prio1 prio0 w 0x1e canxttsrh r tsr15 tsr14 tsr13 tsr12 tsr11 tsr10 tsr9 tsr8 w 0x1f canxttsrl r tsr7 tsr6 tsr5 tsr4 tsr3 tsr2 tsr1 tsr0 w 0x0180?x023f reserved space address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0180 0x023f reserved r00000000 w 0x0240?x027f pim (port integration module) (sheet 1 of 3) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0240 ptt r ptt7 ptt6 ptt5 ptt4 ptt3 ptt2 ptt1 ptt0 w 0x0241 ptit r ptit7 ptit6 ptit5 ptit4 ptit3 ptit2 ptit1 ptit0 w 0x0242 ddrt r ddrt7 ddrt7 ddrt5 ddrt4 ddrt3 ddrt2 ddrt1 ddrt0 w table 1-6. detailed mscan foreground receive and transmit buffer layout (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 60 freescale semiconductor 0x0243 rdrt r rdrt7 rdrt6 rdrt5 rdrt4 rdrt3 rdrt2 rdrt1 rdrt0 w 0x0244 pert r pert7 pert6 pert5 pert4 pert3 pert2 pert1 pert0 w 0x0245 ppst r ppst7 ppst6 ppst5 ppst4 ppst3 ppst2 ppst1 ppst0 w 0x0246 reserved r00000000 w 0x0247 reserved r00000000 w 0x0248 pts r pts7 pts6 pts5 pts4 pts3 pts2 pts1 pts0 w 0x0249 ptis r ptis7 ptis6 ptis5 ptis4 ptis3 ptis2 ptis1 ptis0 w 0x024a ddrs r ddrs7 ddrs7 ddrs5 ddrs4 ddrs3 ddrs2 ddrs1 ddrs0 w 0x024b rdrs r rdrs7 rdrs6 rdrs5 rdrs4 rdrs3 rdrs2 rdrs1 rdrs0 w 0x024c pers r pers7 pers6 pers5 pers4 pers3 pers2 pers1 pers0 w 0x024d ppss r ppss7 ppss6 ppss5 ppss4 ppss3 ppss2 ppss1 ppss0 w 0x024e woms r woms7 woms6 woms5 woms4 woms3 woms2 woms1 woms0 w 0x024f reserved r00000000 w 0x0250 ptm r ptm7 ptm6 ptm5 ptm4 ptm3 ptm2 ptm1 ptm0 w 0x0251 ptim r ptim7 ptim6 ptim5 ptim4 ptim3 ptim2 ptim1 ptim0 w 0x0252 ddrm r ddrm7 ddrm7 ddrm5 ddrm4 ddrm3 ddrm2 ddrm1 ddrm0 w 0x0253 rdrm r rdrm7 rdrm6 rdrm5 rdrm4 rdrm3 rdrm2 rdrm1 rdrm0 w 0x0254 perm r perm7 perm6 perm5 perm4 perm3 perm2 perm1 perm0 w 0x0255 ppsm r ppsm7 ppsm6 ppsm5 ppsm4 ppsm3 ppsm2 ppsm1 ppsm0 w 0x0256 womm r womm7 womm6 womm5 womm4 womm3 womm2 womm1 womm0 w 0x0257 modrr r0 modrr6 modrr5 modrr4 modrr3 modrr2 modrr1 modrr0 w 0x0258 ptp r ptp7 ptp6 ptp5 ptp4 ptp3 ptp2 ptp1 ptp0 w 0x0259 ptip r ptip7 ptip6 ptip5 ptip4 ptip3 ptip2 ptip1 ptip0 w 0x0240?x027f pim (port integration module) (sheet 2 of 3) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 61 0x025a ddrp r ddrp7 ddrp7 ddrp5 ddrp4 ddrp3 ddrp2 ddrp1 ddrp0 w 0x025b rdrp r rdrp7 rdrp6 rdrp5 rdrp4 rdrp3 rdrp2 rdrp1 rdrp0 w 0x025c perp r perp7 perp6 perp5 perp4 perp3 perp2 perp1 perp0 w 0x025d ppsp r ppsp7 ppsp6 ppsp5 ppsp4 ppsp3 ppsp2 ppsp1 ppss0 w 0x025e piep r piep7 piep6 piep5 piep4 piep3 piep2 piep1 piep0 w 0x025f pifp r pifp7 pifp6 pifp5 pifp4 pifp3 pifp2 pifp1 pifp0 w 0x0260 pth r pth7 pth6 pth5 pth4 pth3 pth2 pth1 pth0 w 0x0261 ptih r ptih7 ptih6 ptih5 ptih4 ptih3 ptih2 ptih1 ptih0 w 0x0262 ddrh r ddrh7 ddrh7 ddrh5 ddrh4 ddrh3 ddrh2 ddrh1 ddrh0 w 0x0263 rdrh r rdrh7 rdrh6 rdrh5 rdrh4 rdrh3 rdrh2 rdrh1 rdrh0 w 0x0264 perh r perh7 perh6 perh5 perh4 perh3 perh2 perh1 perh0 w 0x0265 ppsh r ppsh7 ppsh6 ppsh5 ppsh4 ppsh3 ppsh2 ppsh1 ppsh0 w 0x0266 pieh r pieh7 pieh6 pieh5 pieh4 pieh3 pieh2 pieh1 pieh0 w 0x0267 pifh r pifh7 pifh6 pifh5 pifh4 pifh3 pifh2 pifh1 pifh0 w 0x0268 ptj r ptj7 ptj6 0000 ptj1 ptj0 w 0x0269 ptij r ptij7 ptij6 0 0 0 0 ptij1 ptij0 w 0x026a ddrj r ddrj7 ddrj7 0000 ddrj1 ddrj0 w 0x026b rdrj r rdrj7 rdrj6 0000 rdrj1 rdrj0 w 0x026c perj r perj7 perj6 0000 perj1 perj0 w 0x026d ppsj r ppsj7 ppsj6 0000 ppsj1 ppsj0 w 0x026e piej r piej7 piej6 0000 piej1 piej0 w 0x026f pifj r pifj7 pifj6 0000 pifj1 pifj0 w 0x0270 0x027f reserved r 0x0240?x027f pim (port integration module) (sheet 3 of 3) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 62 freescale semiconductor 0x0280?x02bf can4 (mscan) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x0280 can4ctl0 r rxfrm rxact cswai synch time wupe slprq initrq w 0x0281 can4ctl1 r cane clksrc loopb listen 0 wupm slpak initak w 0x0282 can4btr0 r sjw1 sjw0 brp5 brp4 brp3 brp2 brp1 brp0 w 0x0283 can4btr1 r samp tseg22 tseg21 tseg20 tseg13 tseg12 tseg11 tseg10 w 0x0284 can4rflg r wupif cscif rstat1 rstat0 tstat1 tstat0 ovrif rxf w 0x0285 can4rier r wupie cscie rstate1 rstate0 tstate1 tstate0 ovrie rxfie w 0x0286 can4tflg r00000 txe2 txe1 txe0 w 0x0287 can4tier r00000 txeie2 txeie1 txeie0 w 0x0288 can4tarq r00000 abtrq2 abtrq1 abtrq0 w 0x0289 can4taak r 0 0 0 0 0 abtak2 abtak1 abtak0 w 0x028a can4tbsel r00000 tx2 tx1 tx0 w 0x028b can4idac r0 0 idam1 idam0 0 idhit2 idhit1 idhit0 w 0x028c reserved r00000000 w 0x028d reserved r00000000 w 0x028e can4rxerr r rxerr7 rxerr6 rxerr5 rxerr4 rxerr3 rxerr2 rxerr1 rxerr0 w 0x028f can4txerr r txerr7 txerr6 txerr5 txerr4 txerr3 txerr2 txerr1 txerr0 w 0x0290 can4idar0 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x0291 can4idar1 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x0292 can4idar2 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x0293 can4idar3 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x0294 can4idmr0 r am7 am6 am5 am4 am3 am2 am1 am0 w 0x0295 can4idmr1 r am7 am6 am5 am4 am3 am2 am1 am0 w chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 63 0x0296 can4idmr2 r am7 am6 am5 am4 am3 am2 am1 am0 w 0x0297 can4idmr3 r am7 am6 am5 am4 am3 am2 am1 am0 w 0x0298 can4idar4 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x0299 can4idar5 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x029a can4idar6 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x029b can4idar7 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w 0x029c can4idmr4 r am7 am6 am5 am4 am3 am2 am1 am0 w 0x029d can4idmr5 r am7 am6 am5 am4 am3 am2 am1 am0 w 0x029e can4idmr6 r am7 am6 am5 am4 am3 am2 am1 am0 w 0x029f can4idmr7 r am7 am6 am5 am4 am3 am2 am1 am0 w 0x02a0 0x02af can4rxfg r foreground receive buffer (see table 1-6 ) w 0x02b0 0x02bf can4txfg r foreground transmit buffer (see table 1-6 ) w 0x02c0?x02e7 pwm (pulse width modulator 8 bit 8 channel) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x02c0 pwme r pwme7 pwme6 pwme5 pwme4 pwme3 pwme2 pwme1 pwme0 w 0x02c1 pwmpol r ppol7 ppol6 ppol5 ppol4 ppol3 ppol2 ppol1 ppol0 w 0x02c2 pwmclk r pclk7 pclk6 pclk5 pclk4 pclk3 pclk2 pclk1 pclk0 w 0x02c3 pwmprclk r0 pckb2 pckb1 pckb0 0 pcka2 pcka1 pcka0 w 0x02c4 pwmcae r cae7 cae6 cae5 cae4 cae3 cae2 cae1 cae0 w 0x02c5 pwmctl r con67 con45 con23 con01 pswai pfrz 00 w 0x02c6 pwmtst test only r00000000 w 0x02c7 pwmprsc r00000000 w 0x0280?x02bf can4 (mscan) (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 64 freescale semiconductor 0x02c8 pwmscla r bit 7 6 5 4 3 2 1 bit 0 w 0x02c9 pwmsclb r bit 7 6 5 4 3 2 1 bit 0 w 0x02ca pwmscnta r00000000 w 0x02cb pwmscntb r00000000 w 0x02cc pwmcnt0 r bit 7 6 5 4 3 2 1 bit 0 w00000000 0x02cd pwmcnt1 r bit 7 6 5 4 3 2 1 bit 0 w00000000 0x02ce pwmcnt2 r bit 7 6 5 4 3 2 1 bit 0 w00000000 0x02cf pwmcnt3 r bit 7 6 5 4 3 2 1 bit 0 w00000000 0x02d0 pwmcnt4 r bit 7 6 5 4 3 2 1 bit 0 w00000000 0x02d1 pwmcnt5 r bit 7 6 5 4 3 2 1 bit 0 w00000000 0x02d2 pwmcnt6 r bit 7 6 5 4 3 2 1 bit 0 w00000000 0x02d3 pwmcnt7 r bit 7 6 5 4 3 2 1 bit 0 w00000000 0x02d4 pwmper0 r bit 7 6 5 4 3 2 1 bit 0 w 0x02d5 pwmper1 r bit 7 6 5 4 3 2 1 bit 0 w 0x02d6 pwmper2 r bit 7 6 5 4 3 2 1 bit 0 w 0x02d7 pwmper3 r bit 7 6 5 4 3 2 1 bit 0 w 0x02d8 pwmper4 r bit 7 6 5 4 3 2 1 bit 0 w 0x02d9 pwmper5 r bit 7 6 5 4 3 2 1 bit 0 w 0x02da pwmper6 r bit 7 6 5 4 3 2 1 bit 0 w 0x02db pwmper7 r bit 7 6 5 4 3 2 1 bit 0 w 0x02dc pwmdty0 r bit 7 6 5 4 3 2 1 bit 0 w 0x02dd pwmdty1 r bit 7 6 5 4 3 2 1 bit 0 w 0x02de pwmdty2 r bit 7 6 5 4 3 2 1 bit 0 w 0x02c0?x02e7 pwm (pulse width modulator 8 bit 8 channel) (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 65 0x02df pwmdty3 r bit 7 6 5 4 3 2 1 bit 0 w 0x02e0 pwmdty4 r bit 7 6 5 4 3 2 1 bit 0 w 0x02e1 pwmdty5 r bit 7 6 5 4 3 2 1 bit 0 w 0x02e2 pwmdty6 r bit 7 6 5 4 3 2 1 bit 0 w 0x02e3 pwmdty7 r bit 7 6 5 4 3 2 1 bit 0 w 0x02e4 pwmsdn r pwmif pwmie p wmrstrt pwmlvl 0 pwm7in pwm7inl pwm7ena w 0x02e5 reserved r00000000 w 0x02e6 reserved r00000000 w 0x02e7 reserved r00000000 w 0x02e8?x03ff reserved space address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 0x02e8 0x03ff reserved r00000000 w 0x02c0?x02e7 pwm (pulse width modulator 8 bit 8 channel) (continued) address name bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 66 freescale semiconductor 1.3.3 part id assignments the part id is located in two 8-bit registers partidh and partidl (addresses 0x001a and 0x001b after reset. the read-only value is a unique part id for each revision of the chip. table 1-7 shows the assigned part id number. the device memory sizes are located in two 8-bit registers memsiz0 and memsiz1 (addresses 0x001c and 0x001d after reset). table 1-8 shows the read-only values of these registers. refer to hcs12 module mapping and control (mmc) block description chapter for further details. table 1-7. assigned part id numbers device mask set number part id 1 1 the coding is as follows: bit 15-12: major family identifier bit 11-8: minor family identifier bit 7-4: major mask set revision number including fab transfers bit 3-0: minor - non full - mask set revision mc9s12kg128 0l74n 0x7100 table 1-8. memory size registers device register name value mc9s12kg128 memsiz0 0x13 mc9s12kg128 memsiz1 0x80 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 67 1.4 system clock description the clock and reset generator provides the internal clock signals for the core and all peripheral modules. figure 1-12 shows the clock connections from the crg to all modules. consult the crg block guide for details on clock generation. figure 1-12. clock connections 1.5 modes of operation eight possible modes determine the operating con?uration of the mc9s12kg128. each mode has an associated default memory map and external bus con?uration controlled by a further pin. three low power modes exist for the device. 1.5.1 chip con?uration summary the operating mode out of reset is determined by the states of the modc, modb, and moda pins during reset ( table 1-9 ). the modc, modb, and moda bits in the mode register show the current operating mode and provide limited mode switching during operation. the states of the modc, modb, and moda pins are latched into these bits on the rising edge of the reset signal. the romctl signal allows the setting of the romon bit in the misc register thus controlling whether the internal flash is visible in the memory crg bus clock core clock extal xtal oscillator clock hcs12 core flash bdm osc cpu mebi mmc int dbg iic ram sci0, sci1 pwm at d eeprom tim spi0, spi1, spi2 can0, can4 pim chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 68 freescale semiconductor map. romon = 1 mean the flash is visible in the memory map. the state of the romctl pin is latched into the romon bit in the misc register on the rising edge of the reset signal. for further explanation on the modes refer to the hcs12 mebi block description chapter. table 1-9. mode selection bkgd = modc pe6 = modb pe5 = moda pk7 = romctl romon bit mode description 0 0 0 x 1 special single chip, bdm allowed and active. bdm is allowed in all other modes but a serial command is required to make bdm active. 00101em ulation expanded narrow, bdm allowed 10 0 1 0 x 0 special test (expanded wide), bdm allowed 01101em ulation expanded wide, bdm allowed 10 1 0 0 x 1 normal single chip, bdm allowed 10100nor mal expanded narrow, bdm allowed 11 1 1 0 x 1 peripheral; bdm allowed but bus operations would cause bus con?cts (must not be used) 11100nor mal expanded wide, bdm allowed 11 table 1-10. clock selection based on pe7 pe7 = xclks description 1 loop controlled pierce oscillator selected 0 full swing pierce oscillator or external clock selected table 1-11. voltage regulator vregen vregen description 1 internal voltage regulator enabled 0 internal voltage regulator disabled, vdd1,2 and vddpll must be supplied externally with 2.5v chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 69 1.5.2 security the device will make available a security feature preventing the unauthorized read and write of the memory contents. this feature allows: protection of the contents of flash, protection of the contents of eeprom, operation in single-chip mode, operation from external memory with internal flash and eeprom disabled. the user must be reminded that part of the security must lie with the user s code. an extreme example would be user s code that dumps the contents of the internal program. this code would defeat the purpose of security. at the same time the user may also wish to put a back door in the user s program. an example of this is the user downloads a key through the sci which allows access to a programming routine that updates parameters stored in eeprom. 1.5.2.1 securing the microcontroller once the user has programmed the flash and eeprom (if desired), the part can be secured by programming the security bits located in the flash module. these non-volatile bits will keep the part secured through resetting the part and through powering down the part. the security byte resides in a portion of the flash array. check the flash block guide for more details on the security con?uration. 1.5.2.2 operation of the secured microcontroller 1.5.2.2.1 normal single chip mode this will be the most common usage of the secured part. everything will appear the same as if the part was not secured with the exception of bdm operation. the bdm operation will be blocked. 1.5.2.2.2 executing from external memory the user may wish to execute from external space with a secured microcontroller. this is accomplished by resetting directly into expanded mode. the internal flash and eeprom will be disabled. bdm operations will be blocked. 1.5.2.3 unsecuring the microcontroller in order to unsecure the microcontroller, the internal flash and eeprom must be erased. this can be done through an external program in expanded mode. once the user has erased the flash and eeprom, the part can be reset into special single chip mode. this invokes a program that veri?s the erasure of the internal flash and eeprom. once this program completes, the user can erase and program the flash security bits to the unsecured state. this is generally done through the bdm, but the user could also change to expanded mode (by writing the mode bits through the bdm) and jumping to an external program (again through bdm commands). note that if the chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 70 freescale semiconductor part goes through a reset before the security bits are reprogrammed to the unsecure state, the part will be secured again. 1.5.3 low power modes the microcontroller features three main low power modes. consult the respective block guide for information on the module behavior in stop, pseudo stop, and wait mode. an important source of information about the clock system is the clock and reset generator guide (crg). 1.5.3.1 stop executing the cpu stop instruction stops all clocks and the oscillator thus putting the chip in fully static mode. wake up from this mode can be done via reset or external interrupts. 1.5.3.2 pseudo stop this mode is entered by executing the cpu stop instruction. in this mode the oscillator is still running and the real time interrupt (rti) or watchdog (cop) sub module can stay active. other peripherals are turned off. this mode consumes more current than the full stop mode, but the wake up time from this mode is signi?antly shorter. 1.5.3.3 wait this mode is entered by executing the cpu wai instruction. in this mode the cpu will not execute instructions. the internal cpu signals (address and data bus) will be fully static. all peripherals stay active. for further power consumption the peripherals can individually turn off their local clocks. 1.5.3.4 run although this is not a low power mode, unused peripheral modules should not be enabled in order to save power. 1.6 resets and interrupts consult the exception processing section of the cpu12 reference manual for information on resets and interrupts. both local masking and ccr masking are included as listed in table 1-12 . system resets can be generated through external control of the reset pin, through the clock and reset generator module crg or through the low voltage reset (lvr) generator of the voltage regulator module. refer to the crg and vreg block description chapters for detailed information on reset generation. 1.6.1 vectors 1.6.1.1 vector table table 1-12 lists interrupt sources and vectors in default order of priority. chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 71 table 1-12. interrupt vector locations vector address interrupt source ccr mask local enable hprio value to elevate 0xfffe, 0xffff external reset, power on reset or low voltage reset (see crg flags register to determine reset source) none none 0xfffc, 0xfffd clock monitor fail reset none pllctl (cme, fcme) 0xfffa, 0xfffb cop failure reset none cop rate select 0xfff8, 0xfff9 unimplemented instruction trap none none 0xfff6, 0xfff7 swi none none 0xfff4, 0xfff5 xirq x bit none 0xfff2, 0xfff3 irq i bit irqcr (irqen) 0xf2 0xfff0, 0xfff1 real time interrupt i bit crgint (rtie) 0xf0 0xffee, 0xffef standard timer channel 0 i bit tie (c0i) 0xee 0xffec, 0xffed standard timer channel 1 i bit tie (c1i) 0xec 0xffea, 0xffeb standard timer channel 2 i bit tie (c2i) 0xea 0xffe8, 0xffe9 standard timer channel 3 i bit tie (c3i) 0xe8 0xffe6, 0xffe7 standard timer channel 4 i bit tie (c4i) 0xe6 0xffe4, 0xffe5 standard timer channel 5 i bit tie (c5i) 0xe4 0xffe2, 0xffe3 standard timer channel 6 i bit tie (c6i) 0xe2 0xffe0, 0xffe1 standard timer channel 7 i bit tie (c7i) 0xe0 0xffde, 0xffdf standard timer over?w i bit tscr2 (toi) 0xde 0xffdc, 0xffdd pulse accumulator over?w i bit pactl (paovi) 0xdc 0xffda, 0xffdb pulse accumulator input edge i bit pactl (pai) 0xda 0xffd8, 0xffd9 spi0 i bit spicr1 (spie, sptie) 0xd8 0xffd6, 0xffd7 sci0 i bit scicr2 (tie, tcie, rie, ilie) 0xd6 0xffd4, 0xffd5 sci1 i bit scicr2 (tie, tcie, rie, ilie) 0xd4 0xffd2, 0xffd3 atd i bit atdctl2 (ascie) 0xd2 0xffd0, 0xffd1 reserved i bit reserved 0xd0 0xffce, 0xffcf port j i bit piej (piej7, piej6, piej1, piej0) 0xce 0xffcc, 0xffcd port h i bit pieh (pieh7?) 0xcc 0xffca, 0xffcb reserved i bit reserved 0xca 0xffc8, 0xffc9 i bit 0xc8 0xffc6, 0xffc7 crg pll lock i bit crgint (lockie) 0xc6 0xffc4, 0xffc5 crg self clock mode i bit crgint (scmie) 0xc4 0xffc2, 0xffc3 flash double fault detect i bit fcnfg (dfdie) 0xc2 chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 72 freescale semiconductor 0xffc0, 0xffc1 iic bus i bit ibcr (ibie) 0xc0 0xffbe, 0xffbf spi1 i bit spicr1 (spie, sptie) 0xbe 0xffbc, 0xffbd spi2 i bit spicr1 (spie, sptie) 0xbc 0xffba, 0xffbb eeprom command i bit ecnfg (ccie, cbeie) 0xba 0xffb8, 0xffb9 flash command i bit fcnfg (ccie, cbeie) 0xb8 0xffb6, 0xffb7 can0 wake-up i bit can0rier (wupie) 0xb6 0xffb4, 0xffb5 can0 errors i bit can0rier (cscie, ovrie) 0xb4 0xffb2, 0xffb3 can0 receive i bit can0rier (rxfie) 0xb2 0xffb0, 0xffb1 can0 transmit i bit can0tier (txeie2?xeie0) 0xb0 0xffae, 0xffaf reserved i bit reserved 0xae 0xffac, 0xffad i bit 0xac 0xffaa, 0xffab i bit 0xaa 0xffa8, 0xffa9 i bit 0xa8 0xffa6, 0xffa7 i bit 0xa6 0xffa4, 0xffa5 i bit 0xa4 0xffa2, 0xffa3 i bit 0xa2 0xffa0, 0xffa1 i bit 0xa0 0xff9e, 0xff9f i bit 0x9e 0xff9c, 0xff9d i bit 0x9c 0xff9a, 0xff9b i bit 0x9a 0xff98, 0xff99 i bit 0x98 0xff96, 0xff97 can4 wake-up i bit can4rier (wupie) 0x96 0xff94, 0xff95 can4 errors i bit can4rier (cscie, ovrie) 0x94 0xff92, 0xff93 can4 receive i bit can4rier (rxfie) 0x92 0xff90, 0xff91 can4 transmit i bit can4tier (txeie2?xeie0) 0x90 0xff8e, 0xff8f port p i bit piep (piep7?) 0x8e 0xff8c, 0xff8d pwm emergency shutdown i bit pwmsdn (pwmie) 0x8c 0xff8a, 0xff8b vreg low voltage interrupt i bit ctrl0 (lvie) 0x8a 0xff80 - 0xff89 reserved i bit reserved 0x80 - 0x89 table 1-12. interrupt vector locations (continued) vector address interrupt source ccr mask local enable hprio value to elevate chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 73 1.6.2 resets resets are a subset of the interrupts featured in table 1-12 . the different sources capable of generating a system reset are summarized in table 1-13 . 1.6.2.1 effects of reset when a reset occurs, mcu registers and control bits are changed to known start-up states. refer to the respective module block description chapters for register reset states. refer to the pim block description chapter for reset configurations of all peripheral module ports. refer to table 1-5 for locations of the memories depending on the operating mode after reset. the ram array is not automatically initialized out of reset. table 1-13. reset summary reset priority source vector power-on reset 1 crg module 0xfffe, 0xffff external reset 1 reset pin 0xfffe, 0xffff low voltage reset 1 vreg module 0xfffe, 0xffff clock monitor reset 2 crg module 0xfffc, 0xfffd cop watchdog reset 3 crg module 0xfffa, 0xfffb chapter 1 mc9s12kg128 device overview (mc9s12kg128v1) mc9s12kg128 data sheet, rev. 1.15 74 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 75 chapter 2 128 kbyte ecc flash module (fts128k1eccv1) 2.1 introduction this document describes the fts128k1ecc module that includes a 128kbyte flash (nonvolatile) memory with built-in error code correction (ecc). the flash memory may be read as either bytes, aligned words, or misaligned words. read access time is one bus cycle for bytes and aligned words, and two bus cycles for misaligned words. the flash memory is ideal for program and data storage for single-supply applications allowing for ?ld reprogramming without requiring external voltage sources for program or erase. program and erase functions are controlled by a command driven interface. the flash module supports both block erase and sector erase. an erased bit reads 1 and a programmed bit reads 0. the high voltage required to program and erase the flash memory is generated internally. it is not possible to read from a flash block while it is being erased or programmed. the ecc logic is included in the flash module with the program and erase operations automatically generating the ecc parity bits. the ecc logic implements a modi?d hamming code capable of correcting single bit faults and detecting double bit faults in each word of the flash memory. caution a flash word must be in the erased state before being programmed. cumulative programming of bits within a flash word is not allowed and will result in invalid data stored. 2.1.1 glossary command write sequence ?a three-step mcu instruction sequence to execute built-in algorithms (including program and erase) on the flash memory. 2.1.2 features 128 kbytes of flash memory comprised of one 128 kbyte block divided into 128 sectors of 1024 bytes with every word (two bytes) accompanied by 6 ecc parity bits single bit fault correction per word during read operations automated program and erase algorithm with generation of ecc parity bits interrupts on flash command completion, command buffer empty and double bit fault detection fast sector erase and word program operation 2-stage command pipeline for faster multi-word program times chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 76 freescale semiconductor sector erase abort feature for critical interrupt response flexible protection scheme to prevent accidental program or erase single power supply for all flash operations including program and erase security feature to prevent unauthorized access to the flash memory code integrity check using built-in data compression 2.1.3 modes of operation program, erase, erase verify, and data compress operations (please refer to section 2.4.1 for details). 2.1.4 block diagram a block diagram of the flash module is shown in figure 2-1 . chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 77 figure 2-1. fts128k1ecc block diagram 2.2 external signal description the flash module contains no signals that connect off-chip. 2.3 memory map and register de?ition this subsection describes the memory map and registers for the flash module. 2.3.1 module memory map the flash memory map is shown in figure 2-2 . the hcs12 architecture places the flash memory addresses between 0x4000 and 0xffff which corresponds to three 16-kbyte pages. the content of the fts128k1ecc oscillator clock divider clock command interface command pipeline comm2 command interrupt request fclk addr2 data2 comm1 addr1 data1 flash block 64k * 22 bits protection security double fault detect interrupt request error detection and correction sector 0 sector 1 sector 127 chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 78 freescale semiconductor hcs12 core ppage register is used to map the logical middle page ranging from address 0x8000 to 0xbfff to any physical 16 kbyte page in the flash memory. by placing 0x3e or 0x3f in the hcs12 core ppage register, the associated 16 kbyte pages appear twice in the mcu memory map. the fprot register, described in section 2.3.2.5, ?lash protection register (fprot) , can be set to globally protect a flash block. however, three separate memory regions, one growing upward from the ?st address in the next-to-last page in the flash block (called the lower region), one growing downward from the last address in the last page in the flash block (called the higher region), and the remaining addresses in the flash block, can be activated for protection. the flash locations of these protectable regions are shown in table 2-2 . the higher address region is mainly targeted to hold the boot loader code because it covers the vector space. the lower address region can be used for eeprom emulation in an mcu without an eeprom module because it can remain unprotected while the remaining addresses are protected from program or erase. security information that allows the mcu to restrict access to the flash module is stored in the flash con?uration ?ld, described in table 2-1 . table 2-1. flash con?uration field unpaged flash address paged flash address (ppage 0x3f) size (bytes) description 0xff00 - 0xff07 0xbf00-0xbf07 8 backdoor comparison key refer to section section 2.6.1, ?nsecuring the mcu using backdoor key access 0xff08 - 0xff0c 0xbf08-0xbf0c 5 reserved 0xff0d 0xbf0d 1 flash protection byte refer to section 2.3.2.5, ?lash protection register (fprot) 0xff0e 0xbf0e 1 reserved 0xff0f 0xbf0f 1 flash security byte refer to section 2.3.2.2, ?lash security register (fsec) chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 79 figure 2-2. flash memory map flash registers module base + 0x0000 0xff00 - 0xff0f, flash con?uration field module base + 0x000f 0x8000 (16 bytes) flash protected low sectors 1, 2, 4, 8 kbytes flash_start = 0x4000 0x5000 0x4400 0x6000 16k paged memory 0x38 0x39 0x3a 0x3b 0x3e 0x3c 0x3d 0x3e 0x3f note: 0x38-0x3f correspond to the ppage register content flash_end = 0xffff 0xf800 0xf000 0xc000 0xe000 flash protected high sectors 2, 4, 8, 16 kbytes 0x3f 0x4800 flash block chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 80 freescale semiconductor the flash module also contains a set of 16 control and status registers located in address space module base + 0x0000 to module base + 0x000f. a summary of these registers is given in table 2-3 while their accessibility in normal and special modes is detailed in section 2.3.2, ?egister descriptions . table 2-2. detailed flash memory map summary mcu address range ppage protectablelower range protectable higher range block relative address 1 1 block relative address for 128 kbyte flash block consists of 17 address bits. 0x4000-0x7fff unpaged (0x3e) 0x4000-0x43ff n.a. 0x18000-0x1bfff 0x4000-0x47ff 0x4000-0x4fff 0x4000-0x5fff 0x8000-0xbfff 0x38 n.a. n.a. 0x00000-0x03fff 0x39 n.a. n.a. 0x04000-0x07fff 0x3a n.a. n.a. 0x08000-0x0bfff 0x3b n.a. n.a. 0x0c000-0x0ffff 0x3c n.a. n.a. 0x10000-0x13fff 0x3d n.a. n.a. 0x14000-0x17fff 0x3e 0x8000-0x83ff n.a. 0x18000-0x1bfff 0x8000-0x87ff 0x8000-0x8fff 0x8000-0x9fff 0x3f n.a. 0xb800-0xbfff 0x1c000-0x1ffff 0xb000-0xbfff 0xa000-0xbfff 0x8000-0xbfff 0xc000-0xffff unpaged (0x3f) n.a. 0xf800-0xffff 0x1c000-0x1ffff 0xf000-0xffff 0xe000-0xffff 0xc000-0xffff table 2-3. flash register map module base + use normal mode access 0x0000 flash clock divider register (fclkdiv) r/w 0x0001 flash security register (fsec) r 0x0002 flash test mode register (ftstmod) r/w 0x0003 flash con?uration register (fcnfg) r/w 0x0004 flash protection register (fprot) r/w chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 81 0x0005 flash status register (fstat) r/w 0x0006 flash command register (fcmd) r/w 0x0007 reserved1 1 r 0x0008 flash high address register (faddrhi) r 0x0009 flash low address register (faddrlo) r 0x000a flash high data register (fdatahi) r 0x000b flash low data register (fdatalo) r 0x000c reserved2 1 r 0x000d reserved3 1 r 0x000e reserved4 1 r 0x000f reserved5 1 r 1 intended for factory test purposes only. table 2-3. flash register map chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 82 freescale semiconductor 2.3.2 register descriptions register name bit 7 654321 bit 0 fclkdiv r fdivld prdiv8 fdiv5 fdiv4 fdiv3 fdiv2 fdiv1 fdiv0 w fsec r keyen rnv5 rnv4 rnv3 rnv2 sec w ftstmod r 00000000 w fcnfg r cbeie ccie keyacc 00000 w fprot r fpopen rnv6 fphdis fphs fpldis fpls w fstat r cbeif ccif pviol accerr 0 blank 0 0 w fcmd r 0 cmdb w fctl r nv7 nv6 nv5 nv4 nv3 nv2 nv1 nv0 w faddrhi r faddrhi w faddrlo r faddrlo w fdatahi r fdatahi w fdatalo r fdatalo w reserved1 r 00000000 w = unimplemented or reserved figure 2-3. fts128k1ecc register summary chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 83 2.3.2.1 flash clock divider register (fclkdiv) the fclkdiv register is used to control timed events in program and erase algorithms. all bits in the fclkdiv register are readable, bits 6-0 are write once and bit 7 is not writable. 2.3.2.2 flash security register (fsec) the fsec register holds all bits associated with the security of the mcu and flash module. reserved2 r 00000000 w reserved3 r 00000000 w reserved4 r 00000000 w 76543210 r fdivld prdiv8 fdiv5 fdiv4 fdiv3 fdiv2 fdiv1 fdiv0 w reset 00000000 = unimplemented or reserved figure 2-4. flash clock divider register (fclkdiv) table 2-4. fclkdiv field descriptions field description 7 fdivld clock divider loaded. 0 register has not been written. 1 register has been written to since the last reset. 6 prdiv8 enable prescalar by 8 . 0 the oscillator clock is directly fed into the clock divider . 1 the oscillator clock is divided by 8 before feeding into the clock divider. 5-0 fdiv[5:0] clock divider bits ?the combination of prdiv8 and fdiv[5:0] must divide the oscillator clock down to a frequency of 150 khz?00 khz. the maximum divide ratio is 512. please refer to section 2.4.1.1, ?riting the fclkdiv register for more information. register name bit 7 654321 bit 0 = unimplemented or reserved figure 2-3. fts128k1ecc register summary (continued) chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 84 freescale semiconductor all bits in the fsec register are readable but are not writable. the fsec register is loaded from the flash configuration field at address $ff0f during the reset sequence, indicated by f in figure 2-5 . if the dfdif flag in the fstat register is set while reading the security field location during the reset sequence, all bits in the fsec register will be set to leave the module in a secured state with backdoor key access disabled. the security function in the flash module is described in section 2.6, ?lash module security . 76543210 r keyen rnv5 rnv4 rnv3 rnv2 sec w reset f f ffffff = unimplemented or reserved figure 2-5. flash security register (fsec) table 2-5. fsec field descriptions field description 1-0 keyen[1:0] backdoor key security enable bits ?he keyen[1:0] bits de?e the enabling of backdoor key access to the flash module as shown in table 2-6 . 5-2 rnv[5:2] reserved nonvolatile bits ?the rnv[5:2] bits must remain in the erased 1 state for future enhancements. 1-0 sec[1:0] flash security bits the sec[1:0] bits de?e the security state of the mcu as shown in table 2-7 . if the flash module is unsecured using backdoor key access, the sec bits are forced to 10. table 2-6. flash keyen states keyen[1:0] status of backdoor key access 00 disabled 01 1 1 preferred keyen state to disable backdoor key access. disabled 10 enabled 11 disabled table 2-7. flash security states sec[1:0] status of security 00 secured 01 1 1 preferred sec state to set mcu to secured state. secured 10 unsecured 11 secured chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 85 2.3.2.3 flash test mode register (ftstmod) the ftstmod register is used to control flash test features. fdfd is readable and writable while all remaining bits read 0 and are not writable in normal mode. 2.3.2.4 flash con?uration register (fcnfg) the fcnfg register enables the flash interrupts and gates the security backdoor writes. cbeie, ccie, keyacc and dfdie bits are readable and writable while all remaining bits read 0 and are not writable. keyacc is only writable if keyen (see section 2.3.2.2 ) is set to the enabled state. 76543210 r0000 fdfd 000 w reset 00000000 = unimplemented or reserved figure 2-6. flash test mode register (ftstmod) table 2-8. ftstmod field descriptions field description 3 fdfd force double fault detect ?the fdfd bit allows the user to simulate a double bit fault during flash array read operations and check the associated interrupt routine. the fdfd bit is cleared by writing a 0 to fdfd. 0 flash array read operations will set the dfdif ?g in the fstat register only if a double bit fault is detected. 1 any flash array read operation will force the dfdif ?g in the fstat register to be set and an interrupt will be generated as long as the dfdie interrupt enable in the fcnfg register is set. 76543210 r cbeie ccie keyacc 000 bksel w reset 00000000 = unimplemented or reserved figure 2-7. flash con?uration register (fcnfg) chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 86 freescale semiconductor 2.3.2.5 flash protection register (fprot) the fprot register defines which flash sectors are protected against program or erase operations. all bits in the fprot register are readable and writable with restrictions except for rnv[6] which is only readable (see section 2.3.2.6, ?lash protection restrictions ). during reset, the fprot register is loaded from the flash con?uration field at address 0xff0d. to change the flash protection that will be loaded during the reset sequence, the upper sector of the flash memory must be unprotected, then the flash protect/security byte located as described in table 2-1 must be reprogrammed. if the dfdif ?g in the fstat register is set while reading the protection ?ld location during the reset sequence, the fpopen bit will be cleared and remaining bits in the fprot register will be set to leave the flash block fully protected. trying to alter data in any of the protected areas in the flash block will result in a protection violation error and the pviol flag will be set in the fstat register. a mass erase of the flash block is not possible if any of the contained flash sectors are protected. table 2-9. fcnfg field descriptions field description 7 cbeie command buffer empty interrupt enable the cbeie bit enables an interrupt in case of an empty command buffer in the flash module. 0 command buffer empty interrupt disabled. 1 an interrupt will be requested whenever the cbeif ?g (see section 2.3.2.7, ?lash status register (fstat)? is set. 6 ccie command complete interrupt enable the ccie bit enables an interrupt in case all commands have been completed in the flash module. 0 command complete interrupt disabled. 1 an interrupt will be requested whenever the ccif ?g (see section 2.3.2.7, ?lash status register (fstat) ) is set. 5 keyacc enable security key writing 0 flash writes are interpreted as the start of a command write sequence. 1 writes to flash array are interpreted as keys to open the backdoor. reads of the flash array return invalid data. 3 dfdie double fault detect interrupt enable ?the dfdie bit enables an interrupt in case a double bit fault is detected during a flash block operation. 0 double bit fault detect interrupt disabled. 1 an interrupt will be requested whenever the dfdif flag is set (see section 2.3.2.7, ?lash status register (fstat) ?. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 87 table 2-10. fprot field descriptions field description 7 fpopen protection function bit the fpopen bit determines the protection function for program or erase as shown in table 2-11 . 0 fphdis and fpldis bits de?e unprotected address ranges as speci?d by the corresponding fphs[1:0] and fpls[1:0] bits. for an mcu without an eeprom module, the fpopen clear state allows the main part of the flash block to be protected while a small address range can remain unprotected for eeprom emulation. 1 fphdis and fpldis bits enable protection for the address range speci?d by the corresponding fphs[1:0] and fpls[1:0] bits. 6 rnv[6] reserved nonvolatile bit ?the rnv[6] bit must remain in the erased state 1 for future enhancements. 5 fphdis flash protection higher address range disable ?the fphdis bit determines whether there is a protected/unprotected area in the higher address space of the flash block. 0 protection/unprotection enabled 1 protection/unprotection disabled 4:3 fphs[1:0] flash protection higher address size the fphs[1:0] bits determine the size of the protected/unprotected area as shown in table 2-12 . the fphs[1:0] bits can only be written to while the fphdis bit is set. 2 fpldis flash protection lower address range disable ?the fpldis bit determines whether there is a protected/unprotected area in the lower address space of the flash block. 0 protection/unprotection enabled 1 protection/unprotection disabled 1:0 fpls[1:0] flash protection lower address size the fpls[1:0] bits determine the size of the protected/unprotected area as shown in table 2-13 . the fpls[1:0] bits can only be written to while the fpldis bit is set. table 2-11. flash protection function fpopen fphdis fpldis function 1 1 for range sizes, refer to and . 1 1 1 no protection 1 1 0 protected low range 1 0 1 protected high range 1 0 0 protected high and low ranges 0 1 1 full block protected 0 1 0 unprotected low range 0 0 1 unprotected high range 0 0 0 unprotected high and low ranges chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 88 freescale semiconductor all possible flash protection scenarios are illustrated in figure 2-8 . although the protection scheme is loaded from the flash array after reset, it can be changed by the user. this protection scheme can be used by applications requiring re-programming in single-chip mode while providing as much protection as possible if re-programming is not required. table 2-12. flash protection higher address range fphs[1:0] unpaged address range paged address range protected size 00 0xf800-0xffff 0x3f: 0xc800-0xcfff 2 kbytes 01 0xf000-0xffff 0x3f: 0xc000-0xcfff 4 kbytes 10 0xe000-0xffff 0x3f: 0xb000-0xcfff 8 kbytes 11 0xc000-0xffff 0x3f: 0x8000-0xcfff 16 kbytes table 2-13. flash protection lower address range fpls[1:0] unpaged address range paged address range protected size 00 0x4000-0x43ff 0x3e: 0x8000-0x83ff 1 kbyte 01 0x4000-0x47ff 0x3e: 0x8000-0x87ff 2 kbytes 10 0x4000-0x4fff 0x3e: 0x8000-0x8fff 4 kbytes 11 0x4000-0x5fff 0x3e: 0x8000-0x9fff 8 kbytes chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 89 figure 2-8. flash protection scenarios 7 6 5 4 fphs[1:0] fpls[1:0] 3 2 1 0 fphs[1:0] fpls[1:0] fphdis=1 fpldis=1 fphdis=1 fpldis=0 fphdis=0 fpldis=1 fphdis=0 fpldis=0 scenario scenario unprotected region protected region with size protected region protected region with size defined by fpls defined by fphs not defined by fpls, fphs fpopen=1 fpopen=0 ppage 0x38-0x3d ppage 0x3e-0x3f ppage 0x38-0x3d ppage 0x3e-0x3f chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 90 freescale semiconductor 2.3.2.6 flash protection restrictions the general guideline is that flash protection can only be added and not removed. table 2-14 speci?s all valid transitions between flash protection scenarios. any attempt to write an invalid scenario to the fprot register will be ignored and the fprot register will remain unchanged. the contents of the fprot register re?ct the active protection scenario. see the fphs and fpls descriptions for additional restrictions. 2.3.2.7 flash status register (fstat) the fstat register defines the operational status of the module. table 2-14. flash protection scenario transitions from protection scenario to protection scenario 1 1 allowed transitions marked with x. 01234567 0 xxxx 1xx 2xx 3x 4xx 5 xxxx 6xxxx 7 xxxxxxxx 76543210 r cbeif ccif pviol accerr dfdif blank 0 0 w reset 11000000 = unimplemented or reserved figure 2-9. flash status register (fstat - normal mode) 76543210 r cbeif ccif pviol accerr dfdif blank fail 0 w reset 11000000 = unimplemented or reserved figure 2-10. flash status register (fstat - special mode) chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 91 cbeif, pviol, accerr and dfdif are readable and writable, ccif and blank are readable and not writable, remaining bits read 0 and are not writable in normal mode. fail is readable and writable in special mode. fail must be clear when starting a command write sequence. table 2-15. fstat field descriptions field description 7 cbeif command buffer empty interrupt flag ?the cbeif ?g indicates that the address, data and command buffers are empty so that a new command write sequence can be started. the cbeif ?g is cleared by writing a 1 to cbeif. writing a 0 to the cbeif ?g has no effect on cbeif. writing a 0 to cbeif after writing an aligned word to the flash address space but before cbeif is cleared will abort a command write sequence and cause the accerr ?g to be set. writing a 0 to cbeif outside of a command write sequence will not set the accerr ?g. the cbeif ?g is used together with the cbeie bit in the fcnfg register to generate an interrupt request (see figure 2-30 ) . 0 buffers are full. 1 buffers are ready to accept a new command. 6 ccif command complete interrupt flag the ccif ?g indicates that there are no more commands pending. the ccif ?g is cleared when cbeif is clear and sets automatically upon completion of all active and pending commands. the ccif ?g does not set when an active commands completes and a pending command is fetched from the command buffer. writing to the ccif ?g has no effect on ccif. the ccif ?g is used together with the ccie bit in the fcnfg register to generate an interrupt request (see figure 2-30 ). 0 command in progress. 1 all commands are completed. 5 pviol protection violation flag ?the pviol ?g indicates an attempt was made to program or erase an address in a protected area of the flash block during a command write sequence. the pviol ?g is cleared by writing a 1 to pviol. writing a 0 to the pviol ?g has no effect on pviol. while pviol is set, it is not possible to launch a command or start a command write sequence. 0 no failure. 1 a protection violation has occurred. 4 accerr access error flag ?the accerr ?g indicates an illegal access to the flash array caused by either a violation of the command write sequence, issuing an illegal command (illegal combination of the cmdbx bits in the fcmd register), launching the sector erase abort command terminating a sector erase operation early, detection of a double fault or the execution of a cpu stop instruction while a command is executing (ccif = 0). the accerr ?g is cleared by writing a 1 to accerr. writing a 0 to the accerr ?g has no effect on accerr. while accerr is set, it is not possible to launch a command or start a command write sequence. if accerr is set by the detection of a double fault, an erase verify operation or a data compress operation, any buffered command will not launch. 0 no access error detected. 1 access error has occurred. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 92 freescale semiconductor 2.3.2.8 flash command register (fcmd) the fcmd register is the flash command register. all cmdb bits are readable and writable during a command write sequence while bit 7 reads 0 and is not writable. 3 dfdif double fault detect interrupt flag the dfdif ?g indicates that one of the following flash block operations has detected a double bit fault in the stored parity and data bits. array read. erase verify. data compress. reset sequence (reads of the protection and security ?lds stored in the flash memory). when the dfdif ?g is set during a flash array read operation, the data read from the flash module are the data bits read out of the flash array without correction and should be considered invalid. when the dfdif ?g is set during a flash array read, erase verify, data compress or reset sequence operation, the flash block address containing the parity and data bits that caused the dfdif ?g to set will be stored in the faddr register and the parity bits will be stored in the fdata register. the dfdif ?g is cleared by writing a 1 to the accerr bit which is set when the dfdif ?g is set. writing a 0 to the dfdif ?g has no effect on dfdif. the dfdif ?g is used together with the dfdie enable bit to generate an interrupt request (see figure 2-30 ). while dfdif is set, flash array read operations are allowed. if dfdif is not cleared and another double bit fault is detected, the faddr and fdata registers will maintain the contents from the fault that caused the dfdif bit to set. 0 no double bit fault detected. 1 double bit fault detected. 2 blank erase verify operation status flag when the ccif ?g is set after completion of an erase verify command, the blank ?g indicates the result of the erase verify operation. the blank ?g is cleared by the flash module when cbeif is cleared as part of a new valid command write sequence. writing to the blank ?g has no effect on blank. 0 flash block veri?d as not erased. 1 flash block veri?d as erased. 1 fail flag indicating a failed flash operation the fail ?g will set if the erase verify operation fails (flash block veri?d as not erased). the fail ?g will also set if a double bit fault is detected during an array read, erase verify, or data compress operation. the fail flag is cleared by writing a 1 to fail. writing a 0 to the fail flag has no effect on fail. 0 flash operation completed without error. 1 flash operation failed. 76543210 r0 cmdb w reset 00000000 = unimplemented or reserved figure 2-11. flash command register (fcmd - nvm user mode) table 2-15. fstat field descriptions field description chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 93 2.3.2.9 reserved1 this register is reserved for factory testing and is not accessible. all bits read 0 and are not writable. 2.3.2.10 flash address registers (faddr) the faddrhi and faddrlo registers are the flash address registers. table 2-16. fcmd field descriptions field description 6-0 cmdb[6:0] flash command ?valid flash commands are shown in table 2-17 . writing any command other than those listed in table 2-17 sets the accerr ?g in the fstat register. table 2-17. valid flash command list cmdb[6:0] nvm command 0x05 erase verify 0x06 data compress 0x20 word program 0x40 sector erase 0x41 mass erase 0x47 sector erase abort 76543210 r00000000 w reset 00000000 = unimplemented or reserved figure 2-12. reserved1 table 2-18. fctl field descriptions field description 7-0 nv[7:0] nonvolatile bits the nv[7:0] bits are available as nonvolatile bits. refer to the device user guide for proper use of the nv bits. 76543210 r faddrhi w reset 00000000 = unimplemented or reserved figure 2-13. flash address high register (faddrhi) chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 94 freescale semiconductor all faddrhi and faddrlo bits are readable but are not writable. after an array write as part of a command write sequence, the faddr registers will contain the mapped mcu address written. if a double bit fault is detected, as indicated by the setting of the dfdif bit in the fstat register, the faulty flash block address is stored in the faddr registers as a word address. the faulty flash block address remains readable until the start of the next command write sequence. the mapping of the faddr registers to the mcu address is shown in figure 2-15 and figure 2-16 . figure 2-15. faddr to mcu address mapping (paged) figure 2-16. faddr to mcu address mapping (unpaged) 76543210 r faddrlo w reset 00000000 = unimplemented or reserved figure 2-14. flash address low register (faddrlo) ab1 ab2 ab3 ab4 ab5 ab6 ab7 ab8 ab9 ab10 ab11 ab12 ab13 byte select faddrlo[7:0] faddrhi[7:0] mcu address faddr register ppage register pix2 pix1 pix0 1 1 1 0 1 ab0 ab1 ab2 ab3 ab4 ab5 ab6 ab7 ab8 ab9 ab10 ab11 ab12 ab13 byte select faddrlo[7:0] faddrhi[4:0] mcu address (0x4000-0x7fff) faddr register 1 0 ab0 ab1 ab2 ab3 ab4 ab5 ab6 ab7 ab8 ab9 ab10 ab11 ab12 ab13 byte select mcu address (0xc000-0xffff) 1 1 ab0 1 0 1 1 chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 95 2.3.2.11 flash data registers (fdata) the fdatahi and fdatalo registers are the flash data registers. all fdatahi and fdatalo bits are readable but are not writable. after an array write as part of a command write sequence, the fdata registers will contain the data written. at the completion of a data compress operation, the resulting 16-bit signature is stored in the fdata registers. the data compression signature is readable in the fdata registers until a new command write sequence is started or a double bit fault is detected in a flash array read operation . if a double bit fault is detected during a flash array read, erase verify or data compress operation, the parity bits stored in the flash array at the failed location will be stored in the lower six bits of fdatalo. the faulty parity bits remain readable until the start of the next command write sequence. 2.3.2.12 reserved2 this register is reserved for factory testing and is not accessible. all bits read 0 and are not writable. 2.3.2.13 reserved3 this register is reserved for factory testing and is not accessible. 76543210 r fdatahi w reset 00000000 = unimplemented or reserved figure 2-17. flash data high register (fdatahi) 76543210 r fdatalo w reset 00000000 = unimplemented or reserved figure 2-18. flash data low register (fdatalo) 76543210 r00000000 w reset 00000000 = unimplemented or reserved figure 2-19. reserved2 chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 96 freescale semiconductor all bits read 0 and are not writable. 2.3.2.14 reserved4 this register is reserved for factory testing and is not accessible. all bits read 0 and are not writable. 2.3.2.15 reserved5 this register is reserved for factory testing and is not accessible. all bits read 0 and are not writable. 2.4 functional description 2.4.1 flash command operations write and read operations are both used for the program, erase, erase verify, and data compress algorithms described in this subsection. the program and erase algorithms are time controlled by a state machine whose timebase, fclk, is derived from the oscillator clock via a programmable divider. the command 76543210 r00000000 w reset 00000000 = unimplemented or reserved figure 2-20. reserved3 76543210 r00000000 w reset 00000000 = unimplemented or reserved figure 2-21. reserved4 76543210 r00000000 w reset 00000000 = unimplemented or reserved figure 2-22. reserved5 chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 97 register as well as the associated address and data registers operate as a buffer and a register (2-stage fifo) so that a second command along with the necessary data and address can be stored to the buffer while the ?st command remains in progress. this pipelined operation allows a time optimization when programming more than one word on a speci? row in the flash block as the high voltage generation can be kept active in between two programming commands. the pipelined operation also allows a simpli?ation of command launching. buffer empty as well as command completion are signalled by ?gs in the flash status register with interrupts generated, if enabled. the next paragraphs describe: 1. how to write the fclkdiv register. 2. command write sequences used to program, erase, and verify the flash memory. 3. valid flash commands. 4. effects resulting from illegal flash command write sequences or aborting flash operations. 2.4.1.1 writing the fclkdiv register prior to issuing any program, erase, erase verify, or data compress command, it is first necessary to write the fclkdiv register to divide the oscillator clock down to within the 150 khz to 200 khz range. because the program and erase timings are also a function of the bus clock, the fclkdiv determination must take this information into account. if we de?e: fclk as the clock of the flash timing control block, tbus as the period of the bus clock, and int(x) as taking the integer part of x (e.g. int(4.323)=4). then, fclkdiv register bits prdiv8 and fdiv[5:0] are to be set as described in figure 2-23 . for example, if the oscillator clock frequency is 950 khz and the bus clock frequency is 10 mhz, fclkdiv bits fdiv[5:0] must be set to 4 (000100) and bit prdiv8 set to 0. the resulting fclk frequency is then 190 khz. as a result, the flash program and erase algorithm timings are increased over the optimum target by: caution program and erase command execution time will increase proportionally with the period of fclk. because of the impact of clock synchronization on the accuracy of the functional timings, programming or erasing the flash memory cannot be performed if the bus clock runs at less than 1 mhz. programming or erasing the flash memory with fclk < 150 khz must be avoided. setting fclkdiv to a value such that fclk < 150 khz can destroy the flash memory due to overstress. setting fclkdiv to a value such that (1/fclk + tbus) < 5 s can result in incomplete programming or erasure of the flash memory cells. 200 190 () 200 ? 100 5% = chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 98 freescale semiconductor if the fclkdiv register is written, the fdivld bit is set automatically. if the fdivld bit is 0, the fclkdiv register has not been written since the last reset. flash commands will not be executed if the fclkdiv register has not been written to. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 99 figure 2-23. determination procedure for prdiv8 and fdiv bits prdiv8=1 yes no prdiv8=0 (reset) fclk=(prdclk)/(1+fdiv[5:0]) prdclk=oscillator_clock prdclk=oscillator_clock/8 prdclk[mhz]*(5+tbus[ s]) no fdiv[5:0]=prdclk[mhz]*(5+tbus[ s])-1 yes start tbus < 1 s? an integer? fdiv[5:0]=int(prdclk[mhz]*(5+tbus[ s])) 1/fclk[mhz] + tbus[ s] > 5 and fclk > 0.15 mhz ? end yes no fdiv[5:0] > 4? all commands impossible yes no all commands impossible no try to decrease tbus yes oscillator clock > 12.8 mhz? chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 100 freescale semiconductor 2.4.1.2 command write sequence the flash command controller is used to supervise the command write sequence to execute program, erase, erase verify, and data compress algorithms. before starting a command write sequence, the accerr and pviol flags in the fstat register must be clear (see section 2.3.2.7, ?lash status register (fstat) ) and the cbeif flag must be tested to determine the state of the address, data, and command buffers. if the cbeif flag is set, indicating the buffers are empty, a new command write sequence can be started. if the cbeif flag is clear, indicating the buffers are not available, a new command write sequence will overwrite the contents of the address, data, and command buffers. a command write sequence consists of three steps which must be strictly adhered to with writes to the flash module not permitted between the steps. however, flash register and array reads are allowed during a command write sequence. a command write sequence consists of the following steps: 1. write an aligned data word to a valid flash array address. the address and data will be stored in the address and data buffers, respectively. if the cbeif ?g is clear when the flash array write occurs, the contents of the address and data buffers will be overwritten and the cbeif ?g will be set. 2. write a valid command to the fcmd register. a) for the erase verify command (see section 2.4.1.3.1, ?rase verify command ), the contents of the data buffer are ignored and all address bits in the address buffer are ignored. b) for the data compress command (see section 2.4.1.3.2, ?ata compress command ), the contents of the data buffer represents the number of consecutive words to read for data compression and the contents of the address buffer represents the starting address. c) for the program command (see section 2.4.1.3.3, ?rogram command ), the contents of the data buffer will be programmed to the address speci?d in the address buffer with all address bits valid. d) for the sector erase command (see section 2.4.1.3.4, ?ector erase command ), the contents of the data buffer are ignored and address bits [9:0] contained in the address buffer are ignored. e) for the mass erase command (see section 2.4.1.3.5, ?ass erase command ), the contents of the data buffer and address buffer are ignored. f) for the sector erase abort command (see section 2.4.1.3.6, ?ector erase abort command ), the contents of the data buffer and address buffer are ignored. 3. clear the cbeif ?g by writing a 1 to cbeif to launch the command. when the cbeif ?g is cleared, the ccif ?g is cleared on the same bus cycle by internal hardware indicating that the command was successfully launched. for all command write sequences except data compress and sector erase abort, the cbeif ?g will set four bus cycles after the ccif ?g is cleared indicating that the address, data, and command buffers are ready for a new command write sequence to begin. for data compress and sector erase abort operations, the cbeif ?g will remain clear until the operation completes. a command write sequence can be aborted prior to clearing the cbeif ?g by writing a 0 to the cbeif ?g and will result in the accerr ?g being set. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 101 except for the sector erase abort command, a buffered command will wait for the active operation to be completed before being launched. the sector erase abort command is launched when the cbeif ?g is cleared as part of a sector erase abort command write sequence. after a command is launched, the completion of the command operation is indicated by the setting of the ccif ?g. the ccif ?g only sets when all active and buffered commands have been completed. 2.4.1.3 valid flash commands table 2-19 summarizes the valid flash commands along with the effects of the commands on the flash block. caution a flash word must be in the erased state before being programmed. cumulative programming of bits within a flash word is not allowed and will result in invalid data stored. table 2-19. valid flash command description fcmdb nvm command function on flash memory 0x05 erase verify verify all memory bytes in the flash block are erased. if the flash block is erased, the blank ?g in the fstat register will set upon command completion. 0x06 data compress compress data from a selected portion of the flash block. the resulting signature is stored in the fdata register. 0x20 program program a word (two bytes) in the flash block. 0x40 sector erase erase all memory bytes in a sector of the flash block. 0x41 mass erase erase all memory bytes in the flash block. a mass erase of the full flash block is only possible when fpldis, fphdis, and fpopen bits in the fprot register are set prior to launching the command. 0x47 sector erase abort abort the sector erase operation. the sector erase operation will terminate according to a set procedure. the flash sector must not be considered erased if the accerr ?g is set upon command completion. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 102 freescale semiconductor 2.4.1.3.1 erase verify command the erase verify operation is used to confirm that a flash block is erased. after launching the erase verify command, the ccif flag in the fstat register will set after the operation has completed unless a second command has been buffered. the number of bus cycles required to execute the erase verify operation is equal to the number of addresses in the flash block plus 12 bus cycles as measured from the time the cbeif flag is cleared until the ccif flag is set. the result of the erase verify operation is reflected in the state of the blank flag in the fstat register. if the blank flag is set in the fstat register, the flash memory is erased. if the ecc logic detects a double bit fault during the erase verify operation, the operation will terminate immediately and set the dfdif and accerr flags in the fstat register. the faulty address will be stored in the faddr registers and the ecc parity bits read at the faulty address will be stored in the fdatalo register. the ccif flag will set after the dfdif flag is set and the faulty information is stored in the faddr and fdatalo registers. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 103 figure 2-24. example erase verify command flow write: register fclkdiv read: register fclkdiv bit fdivld set? write: flash block address write: register fcmd erase verify command 0x05 write: register fstat yes no clear bit cbeif 0x80 clock register loaded check 1. 2. 3. clear bit accerr 0x10 write: register fstat yes access error check read: register fstat no no and dummy data bit polling for command completion check read: register fstat note: command write sequence aborted by writing 0x00 to fstat register. note: command write sequence aborted by writing 0x00 to fstat register. ccif set? bit accerr set? bit exit yes blank set? bit yes no yes double bit fault detection check no dfdif set? bit clear bit dfdif 0x08 write: register fstat mass erase flash block yes no dfdif set? bit flash block not erased blank status check chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 104 freescale semiconductor 2.4.1.3.2 data compress command the data compress command is used to check flash code integrity by compressing data from a selected portion of the flash block into a signature analyzer. the starting address for the data compress operation is defined by the address written during the command write sequence. the number of consecutive word addresses compressed is defined by the data written during the command write sequence. if the data value written is 0x0000, 64k addresses or 128 kbytes will be compressed. after launching the data compress command, the ccif flag in the fstat register will set after the data compress operation has completed. the number of bus cycles required to execute the data compress operation is equal to two times the number of addresses read plus 20 bus cycles as measured from the time the cbeif flag is cleared until the ccif flag is set. after the ccif flag is set, the signature generated by the data compress operation is available in the fdata register. the signature in the fdata register can be compared to the expected signature to determine the integrity of the selected data stored in the flash block. if the last address of the flash block is reached during the data compress operation, data compression will continue with the starting address of the flash block. note since the fdata register (or data buffer) is written to as part of the data compress operation, a command write sequence is not allowed to be buffered behind a data compress command write sequence. the cbeif ?g will not set after launching the data compress command to indicate that a command must not be buffered behind it. if an attempt is made to start a new command write sequence with a data compress operation active, the accerr ?g in the fstat register will be set. a new command write sequence must only be started after reading the signature stored in the fdata register. a flash array read that generates a double bit fault will overwrite the contents of the fdata register. in order to take corrective action, it is recommended that the data compress command be executed on a flash sector or subset of a flash sector. if the data compress operation on a flash sector returns an invalid signature, the flash sector must be erased using the sector erase command and then reprogrammed using the program command. the data compress command can be used to verify that a sector or sequential set of sectors are erased. if the ecc logic detects a double bit fault during the data compress operation, the operation will terminate immediately and set the dfdif and accerr flags in the fstat register. the faulty address will be stored in the faddr registers and the ecc parity bits read at the faulty address will be stored in the fdatalo register. the ccif flag will set after the dfdif flag is set and the faulty information is stored in the faddr and fdatalo registers. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 105 figure 2-25. example data compress command flow write: register fclkdiv read: register fclkdiv bit fdivld set? write: flash address to start write: register fcmd data compress command 0x06 write: register fstat yes no clear bit cbeif 0x80 clock register loaded check 1. 2. 3. read: register fstat no exit compression and number of bit polling for command completion check read: register fstat yes note: command write sequence aborted by writing 0x00 to fstat register. note: command write sequence aborted by writing 0x00 to fstat register. ccif set? bit word addresses to compress read: register fdata data compress signature no erase and reprogram yes signature valid? signature flash region compressed compared to known value yes double bit fault detection check no dfdif set? bit clear bit accerr 0x10 write: register fstat yes access error check accerr set? bit yes no dfdif set? bit clear bit dfdif 0x08 write: register fstat no chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 106 freescale semiconductor 2.4.1.3.3 program command the program command is used to program a previously erased word in the flash memory using an embedded algorithm. if the word to be programmed is in a protected area of the flash block, the pviol flag in the fstat register will set and the program command will not launch. after the program command has successfully launched, the ccif flag in the fstat register will set after the program operation has completed unless a second command has been buffered. a summary of the launching of a program operation is shown in figure 2-26 . figure 2-26. example program command flow write: register fclkdiv read: register fclkdiv bit fdivld set? write: flash address and write: register fcmd program command 0x20 write: register fstat yes no clear bit cbeif 0x80 yes clock register loaded check 1. 2. 3. clear bit accerr 0x10 write: register fstat no yes no protection violation check access error check read: register fstat no no address, data, command buffer empty check next write? yes exit no program data clear bit pviol 0x20 write: register fstat yes bit polling for command completion check read: register fstat yes note: command write sequence aborted by writing 0x00 to fstat register. note: command write sequence aborted by writing 0x00 to fstat register. ccif set? bit cbeif set? bit accerr set? bit pviol set? bit chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 107 2.4.1.3.4 sector erase command the sector erase command is used to erase the addressed sector in the flash memory using an embedded algorithm. if the flash sector to be erased is in a protected area of the flash block, the pviol flag in the fstat register will set and the sector erase command will not launch. after the sector erase command has successfully launched, the ccif flag in the fstat register will set after the sector erase operation has completed unless a second command has been buffered. figure 2-27. example sector erase command flow write: register fclkdiv read: register fclkdiv bit fdivld set? write: flash sector address write: register fcmd sector erase command 0x40 write: register fstat yes no clear bit cbeif 0x80 yes clock register loaded check 1. 2. 3. clear bit accerr 0x10 write: register fstat no yes no protection violation check access error check read: register fstat no no address, data, command buffer empty check next write? yes exit no and dummy data clear bit pviol 0x20 write: register fstat yes bit polling for command completion check read: register fstat yes note: command write sequence aborted by writing 0x00 to fstat register. note: command write sequence aborted by writing 0x00 to fstat register. ccif set? bit pviol set? bit accerr set? bit cbeif set? bit chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 108 freescale semiconductor 2.4.1.3.5 mass erase command the mass erase command is used to erase a flash memory block using an embedded algorithm. if the flash block to be erased contains any protected area, the pviol flag in the fstat register will set and the mass erase command will not launch. after the mass erase command has successfully launched, the ccif flag in the fstat register will set after the mass erase operation has completed unless a second command has been buffered. figure 2-28. example mass erase command flow write: register fclkdiv read: register fclkdiv bit fdivld set? write: flash block address write: register fcmd mass erase command 0x41 write: register fstat yes no clear bit cbeif 0x80 yes clock register loaded check 1. 2. 3. clear bit accerr 0x10 write: register fstat no yes no protection violation check access error check read: register fstat ccif set? bit no no address, data, command buffer empty check next write? yes exit no and dummy data clear bit pviol 0x20 write: register fstat yes bit polling for command completion check read: register fstat yes note: command write sequence aborted by writing 0x00 to fstat register. note: command write sequence aborted by writing 0x00 to fstat register. pviol set? bit accerr set? bit cbeif set? bit chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 109 2.4.1.3.6 sector erase abort command the sector erase abort command is used to terminate the sector erase operation so that other sectors in the flash block are available for read and program operations without waiting for the sector erase operation to complete. if the sector erase abort command is launched resulting in the early termination of an active sector erase operation, the accerr flag will set after the operation completes as indicated by the ccif flag being set. the accerr flag sets to inform the user that the sector may not be fully erased and a new sector erase command must be launched before programming any location in that specific sector. if the sector erase abort command is launched but the active sector erase operation completes normally, the accerr flag will not set upon completion of the operation as indicated by the ccif flag being set. therefore, if the accerr flag is not set after the sector erase abort command has completed, the sector being erased when the abort command was launched is fully erased. the maximum number of cycles required to abort a sector erase operation is equal to four fclk periods (see section 2.4.1.1, ?riting the fclkdiv register ) plus five bus cycles as measured from the time the cbeif flag is cleared until the ccif flag is set. note since the accerr bit in the fstat register may be set at the completion of the sector erase abort operation, a command write sequence is not allowed to be buffered behind a sector erase abort command write sequence. the cbeif ?g will not set after launching the sector erase abort command to indicate that a command must not be buffered behind it. if an attempt is made to start a new command write sequence with a sector erase abort operation active, the accerr ?g in the fstat register will be set. a new command write sequence may be started after clearing the accerr ?g, if set. note the sector erase abort command must be used sparingly because a sector erase operation that is aborted counts as a complete program/erase cycle. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 110 freescale semiconductor figure 2-29. example sector erase abort command flow write: dummy flash address write: register fcmd sector erase abort cmd 0x47 write: register fstat clear bit cbeif 0x80 1. 2. 3. read: register fstat no exit and dummy data bit polling for command completion check read: register fstat yes note: command write sequence aborted by writing 0x00 to fstat register. note: command write sequence aborted by writing 0x00 to fstat register. ccif set? bit execute sector erase command flow no bit polling for command completion check read: register fstat yes ccif set? bit no yes abort needed? erase exit clear bit accerr 0x10 write: register fstat yes no access error check accerr set? bit exit sector erase completed sector erase aborted chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 111 2.4.1.4 illegal flash operations the accerr flag will be set during the command write sequence if any of the following illegal steps are performed, causing the command write sequence to immediately abort: 1. writing to a flash address before initializing the fclkdiv register. 2. writing a byte or misaligned word to a valid flash address. 3. starting a command write sequence while a data compress operation is active. 4. starting a command write sequence while a sector erase abort operation is active. 5. writing a second word to a flash address in the same command write sequence. 6. writing to any flash register other than fcmd after writing a word to a flash address. 7. writing a second command to the fcmd register in the same command write sequence. 8. writing an invalid command to the fcmd register. 9. when security is enabled, writing a command other than mass erase to the fcmd register when the write originates from a non-secure memory location or from the background debug mode. 10. writing to any flash register other than fstat (to clear cbeif) after writing to the fcmd register. 11. writing a 0 to the cbeif ?g in the fstat register to abort a command write sequence. the accerr flag will not be set if any flash register is read during a valid command write sequence. the accerr ?g will also be set if any of the following events occur: 1. launching the sector erase abort command while a sector erase operation is active which results in the early termination of the sector erase operation (see section 2.4.1.3.6, ?ector erase abort command ) 2. a double bit fault is detected in any of the following flash operations: a) array read b) erase verify c) data compress d) reset sequence array read (con?uration field) 3. the mcu enters stop mode and a program or erase operation is in progress. the operation is aborted immediately and any pending command is purged (see section 2.5.2, ?top mode ). if the flash memory is read during execution of an algorithm (i.e., ccif flag in the fstat register is low), the read operation will return invalid data and the accerr flag will not be set. if the accerr flag is set in the fstat register, the user must clear the accerr flag before starting another command write sequence (see section 2.3.2.7, ?lash status register (fstat) ). the pviol flag will be set after the command is written to the fcmd register during a command write sequence if any of the following illegal operations are attempted, causing the command write sequence to immediately abort: 1. writing the program command if the address written in the command write sequence was in a protected area of the flash memory. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 112 freescale semiconductor 2. writing the sector erase command if the address written in the command write sequence was in a protected area of the flash memory. 3. writing the mass erase command while any flash protection is enabled. if the pviol flag is set in the fstat register, the user must clear the pviol flag before starting another command write sequence (see section 2.3.2.7, ?lash status register (fstat) ). 2.5 operating modes 2.5.1 wait mode if a command is active (ccif = 0) when the mcu enters wait mode, the active command and any buffered command will be completed. the flash module can recover the mcu from wait mode if the cbeif and ccif interrupts are enabled ( section 2.8, ?nterrupts ). 2.5.2 stop mode if a command is active (ccif = 0) when the mcu enters stop mode, the operation will be aborted and, if the operation is program or erase, the flash array data being programmed or erased may be corrupted and the ccif and accerr flags will be set. if active, the high voltage circuitry to the flash memory will immediately be switched off when entering stop mode. upon exit from stop mode, the cbeif flag is set and any buffered command will not be launched. the accerr flag must be cleared before starting a command write sequence (see section 2.4.1.2, ?ommand write sequence ). note as active commands are immediately aborted when the mcu enters stop mode, it is strongly recommended that the user does not use the stop instruction during program or erase operations. 2.5.3 background debug mode in background debug mode (bdm), the fprot register is writable. if the mcu is unsecured, then all flash commands listed in table 2-19 can be executed. 2.6 flash module security the flash module provides the necessary security information to the mcu. after each reset, the flash module determines the security state of the mcu as de?ed in section 2.3.2.2, ?lash security register (fsec) . the contents of the flash security byte at 0xff0f in the flash con?uration ?ld must be changed directly by programming 0xff0f when the mcu is unsecured and the higher address sector is unprotected. if the chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 113 flash security byte remains in a secured state, any reset will cause the mcu to initialize to a secure operating mode. 2.6.1 unsecuring the mcu using backdoor key access the mcu may be unsecured by using the backdoor key access feature which requires knowledge of the contents of the backdoor keys (four 16-bit words programmed at addresses 0xff00?xff07). if the keyen[1:0] bits are in the enabled state (see section 2.3.2.2, ?lash security register (fsec) ) and the keyacc bit is set, a write to a backdoor key address in the flash memory triggers a comparison between the written data and the backdoor key data stored in the flash memory. if all four words of data are written to the correct addresses in the correct order and the data matches the backdoor keys stored in the flash memory, the mcu will be unsecured. the data must be written to the backdoor keys sequentially starting with 0xff00?xff01 and ending with 0xff06?xff07. 0x0000 and 0xffff are not permitted as backdoor keys. while the keyacc bit is set, reads of the flash memory will return invalid data. the user code stored in the flash memory must have a method of receiving the backdoor key from an external stimulus. this external stimulus would typically be through one of the on-chip serial ports. if the keyen[1:0] bits are in the enabled state (see section 2.3.2.2, ?lash security register (fsec) ), the mcu can be unsecured by the backdoor access sequence described below: 1. set the keyacc bit in the flash con?uration register (fcnfg). 2. write the correct four 16-bit words to flash addresses 0xff00?xff07 sequentially starting with 0xff00. 3. clear the keyacc bit. 4. if all four 16-bit words match the backdoor keys stored in flash addresses 0xff00?xff07, the mcu is unsecured and the sec[1:0] bits in the fsec register are forced to the unsecure state of 1:0. the backdoor key access sequence is monitored by an internal security state machine. an illegal operation during the backdoor key access sequence will cause the security state machine to lock, leaving the mcu in the secured state. a reset of the mcu will cause the security state machine to exit the lock state and allow a new backdoor key access sequence to be attempted. the following operations during the backdoor key access sequence will lock the security state machine: 1. if any of the four 16-bit words does not match the backdoor keys programmed in the flash array. double bit faults detected while reading the backdoor keys from the flash array are ignored. 2. if the four 16-bit words are written in the wrong sequence. 3. if more than four 16-bit words are written. 4. if any of the four 16-bit words written are 0x0000 or 0xffff. 5. if the keyacc bit does not remain set while the four 16-bit words are written. 6. if any two of the four 16-bit words are written on successive mcu clock cycles. after the backdoor keys have been correctly matched, the mcu will be unsecured. after the mcu is unsecured, the flash security byte can be programmed to the unsecure state, if desired. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 114 freescale semiconductor in the unsecure state, the user has full control of the contents of the backdoor keys by programming addresses 0xff00?xff07 in the flash con?uration ?ld. the security as de?ed in the flash security byte (0xff0f) is not changed by using the backdoor key access sequence to unsecure. the backdoor keys stored in addresses 0xff00?xff07 are unaffected by the backdoor key access sequence. after the next reset of the mcu, the security state of the flash module is determined by the flash security byte (0xff0f). the backdoor key access sequence has no effect on the program and erase protections de?ed in the flash protection register. it is not possible to unsecure the mcu in special single-chip mode by using the backdoor key access sequence via the background debug mode (bdm). 2.6.2 unsecuring the flash module in special single-chip mode using bdm the mcu can be unsecured in special single-chip mode by erasing the flash module by the following method : reset the mcu into special single-chip mode, delay while the erase test is performed by the bdm secure rom, send bdm commands to disable protection in the flash module, and execute a mass erase command write sequence to erase the flash memory. after the ccif ?g sets to indicate that the mass operation has completed, reset the mcu into special single-chip mode. the bdm secure rom will verify that the flash memory is erased and will assert the unsec bit in the bdm status register. this bdm action will cause the mcu to override the flash security state and the mcu will be unsecured. all bdm commands will be enabled and the flash security byte may be programmed to the unsecure state by the following method: send bdm commands to execute a word program sequence to program the flash security byte to the unsecured state and reset the mcu. 2.7 resets 2.7.1 flash reset sequence on each reset, the flash module executes a reset sequence to hold cpu activity while loading the following registers from the flash memory according to table 2-1 : fprot ?flash protection register (see section 2.3.2.5 ). if a double bit fault is detected during the read of the protection ?ld as part of the reset sequence, the fpopen bit in the fprot register will be clear and remaining bits will be set leaving the flash block fully protected from program and erase. fsec ?flash security register (see section 2.3.2.2 ). if a double bit fault is detected during the read of the security ?ld as part of the reset sequence, all bits in the fsec register will be set leaving the flash module in a secure state with backdoor key access disabled. chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 115 if a double bit fault is detected during array reads as part of the reset sequence, the accerr ?g will set in the fstat register. 2.7.2 reset while flash command active if a reset occurs while any flash command is in progress, that command will be immediately aborted. the state of the word being programmed or the sector / block being erased is not guaranteed. 2.8 interrupts the flash module can generate an interrupt when all flash command operations have completed, when the flash address, data, and command buffers are empty, or when a flash array read or operation has detected a double bit fault. note vector addresses and their relative interrupt priority are determined at the mcu level. 2.8.1 description of flash interrupt operation the logic used for generating interrupts is shown in figure 2-30 . the flash module uses the cbeif and ccif ?gs in combination with the cbie and ccie enable bits to generate the flash command interrupt request. the flash module uses the dfdif ?g in combination with the dfdie enable bit to generate the flash double fault detect interrupt request. table 2-20. flash interrupt sources interrupt source interrupt flag local enable global (ccr) mask flash address, data and command buffers empty cbeif (fstat register) cbeie (fcnfg register) i-bit all flash commands completed ccif (fstat register) ccie (fcnfg register) i-bit flash array read or verify operation detected a double bit fault dfdif (fstat register) dfdie (fcnfg register) i-bit chapter 2 128 kbyte ecc flash module (fts128k1eccv1) mc9s12kg128 data sheet, rev. 1.15 116 freescale semiconductor figure 2-30. flash interrupt implementation for a detailed description of the register bits, refer to section 2.3.2.4, ?lash con?uration register (fcnfg) and section 2.3.2.7, ?lash status register (fstat) . flash command interrupt request cbeie cbeif ccie ccif dfdie dfdif flash double fault detect interrupt request mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 117 chapter 3 2 kbyte eeprom module (eets2kv1) 3.1 introduction this document describes the eets2k module which is a 2 kbyte eeprom (nonvolatile) memory. the eets2k block uses a small sector flash memory to emulate eeprom functionality. it is an array of electrically erasable and programmable, nonvolatile memory. the eeprom memory is organized as 1024 rows of 2 bytes (1 word). the eeprom memory s erase sector size is 2 rows or 2 words (4 bytes). the eeprom memory may be read as either bytes, aligned words, or misaligned words. read access time is one bus cycle for byte and aligned word, and two bus cycles for misaligned words. program and erase functions are controlled by a command driven interface. both sector erase and mass erase of the entire eeprom memory are supported. an erased bit reads 1 and a programmed bit reads 0. the high voltage required to program and erase is generated internally by on-chip charge pumps. it is not possible to read from the eeprom memory while it is being erased or programmed. the eeprom memory is ideal for data storage for single-supply applications allowing for ?ld reprogramming without requiring external programming voltage sources. caution an eeprom word must be in the erased state before being programmed. cumulative programming of bits within a word is not allowed. 3.1.1 glossary command write sequence a three-step mcu instruction sequence to program, erase, or erase verify the eeprom. 3.1.2 features 2 kbytes of eeprom memory minimum erase sector of 4 bytes automated program and erase algorithms interrupts on eeprom command completion and command buffer empty fast sector erase and word program operation 2-stage command pipeline flexible protection scheme for protection against accidental program or erase single power supply program and erase chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 118 freescale semiconductor 3.1.3 modes of operation program and erase operation (please refer to section 3.4.1 for details). 3.1.4 block diagram figure 3-1 shows a block diagram of the eets2k module. figure 3-1. eets2k block diagram 3.2 external signal description the eets2k module contains no signals that connect off chip. 3.3 memory map and register de?ition this section describes the eets2k memory map and registers. 3.3.1 module memory map figure 3-2 shows the eets2k memory map. location of the eeprom array in the mcu memory map is de?ed in the device overview chapter and is re?cted in the initee register contents de?ed in the int block description chapter. shown within the eeprom array are: a protection/reserved ?ld and user-de?ed eeprom protected sectors. the 16-byte protection/reserved ?ld is located in the eeprom array from address 0x07f0 to 0x07ff. a description of this protection/reserved ?ld is given in table 3-1 . eets2k eeprom array 1024 * 16 bits row0 row1 row1023 oscillator clock divider clock command interface command pipeline comm2 registers eeclk addr2 data2 comm1 addr1 data1 command complete interrupt command buffer empty interrupt chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 119 the eeprom module has hardware interlocks which protect data from accidental corruption. a protected sector is located at the higher address end of the eeprom array, just below address 0x07ff. the protected sector in the eeprom array can be sized from 64 bytes to 512 bytes. in addition, the epopen bit in the eprot register, described in section 3.3.2.5, ?eprom protection register (eprot) , can be set to globally protect the entire eeprom array. chip security is de?ed at the mcu level. figure 3-2. eeprom memory map table 3-1. eeprom protection/reserved field address offset size (bytes) description 0x07f0 ?0x07fc 13 reserved 0x07fd 1 eeprom protection byte 0x07fe ?0x07ff 2 reserved eeprom registers module base + 0x0000 eeprom base + 0x07ff 0x07c0 0x07f0 ?0x07ff, eeprom protection/reserved field module base + 0x000b 0x0780 0x0600 (12 bytes) 0x0700 eeprom protected high sectors 64, 128, 192, 256, 320, 384, 448, 512 bytes eeprom base + 0x0000 1536 bytes 0x0740 0x06c0 0x0640 0x0680 eeprom array chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 120 freescale semiconductor the eeprom module also contains a set of 12 control and status registers located in address space module base + 0x0000 to module base + 0x000b. table 3-2 gives an overview of all eets2k registers. table 3-2. eeprom register map module base + register name normal mode access 0x0000 eeprom clock divider register (eclkdiv) r/w 0x0001 reserved1 1 1 intended for factory test purposes only. r 0x0002 reserved2 1 r 0x0003 eeprom con?uration register (ecnfg) r/w 0x0004 eeprom protection register (eprot) r/w 0x0005 eeprom status register (estat) r/w 0x0006 eeprom command register (ecmd) r/w 0x0007 reserved3 1 r 0x0008 eeprom high address register (eaddrhi) r/w 0x0009 eeprom low address register (eaddrlo) r/w 0x000a eeprom high data register (edatahi) r/w 0x000b eeprom low data register (edatalo) r/w chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 121 3.3.2 register descriptions 3.3.2.1 eeprom clock divider register (eclkdiv) the eclkdiv register is used to control timed events in program and erase algorithms. register name bit 7 654321 bit 0 eclkdiv r edivld prdiv8 ediv5 ediv4 ediv3 ediv2 ediv1 ediv0 w reserved1 r 00000000 w reserved2 r 00000000 w ecnfg r cbeie ccie 000000 w eprot r epopen nv6 nv5 nv4 epdis ep2 ep1 epo w estat r cbeif ccif pviol accerr 0 blank 0 0 w ecmd r 0 cmdb6 cmdb5 00 cmdb2 0 cmdb0 w reserved3 r 00000000 w eaddrhi r 000000 eabhi w eaddrlo r eablo w edatahi r edhi w edatalo r edlo w = unimplemented or reserved figure 3-3. eets2k register summary chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 122 freescale semiconductor all bits in the eclkdiv register are readable while bits 6-0 are write once and bit 7 is not writable. 3.3.2.2 reserved1 this register is reserved for factory testing and is not accessible to the user. all bits read 0 and are not writable. 3.3.2.3 reserved2 this register is reserved for factory testing and is not accessible to the user. 76543210 r edivld prdiv8 ediv5 ediv4 ediv3 ediv2 ediv1 ediv0 w reset 0 0 0 00000 = unimplemented or reserved figure 3-4. eeprom clock divider register (eclkdiv) table 3-3. eclkdiv field descriptions field description 7 edivld clock divider loaded 0 register has not been written. 1 register has been written to since the last reset. 6 prdiv8 enable prescaler by 8 0 the oscillator clock is directly fed into the eclkdiv divider. 1 the oscillator clock is divided by 8 before feeding into the clock divider. 5:0 ediv[5:0] clock divider bits ?the combination of prdiv8 and ediv[5:0] must divide the oscillator clock down to a frequency of 150 khz 200 khz. the maximum divide ratio is 512. please refer to section 3.4.1.1, ?riting the eclkdiv register for more information. 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 3-5. reserved1 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 3-6. reserved2 chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 123 all bits read 0 and are not writable. 3.3.2.4 eeprom con?uration register (ecnfg) the ecnfg register enables the eeprom interrupts. cbeie and ccie bits are readable and writable while bits 5-0 read 0 and are not writable. 3.3.2.5 eeprom protection register (eprot) the eprot register de?es which eeprom sectors are protected against program or erase. the eprot register is loaded from eeprom array address 0x07fd during reset, as indicated by the f in figure 3-8 . all bits in the eprot register are readable. bits nv[6:4] are not writable. the epopen and epdis bits in the eprot register can only be written to the protected state (i.e., 0). the ep[2:0] bits can be written anytime until bit epdis is cleared. if the epopen bit is cleared, then the state of the epdis and ep[2:0] bits is irrelevant. 76543210 r cbeie ccie 000000 w reset 0 0 0 00000 = unimplemented or reserved figure 3-7. eeprom con?uration register (ecnfg) table 3-4. ecnfg field descriptions field description 7 cbeie command buffer empty interrupt enable ?the cbeie bit enables the interrupts in case of an empty command buffer in the eeprom. 0 command buffer empty interrupts disabled. 1 an interrupt will be requested whenever the cbeif ?g is set (see section 3.3.2.6, ?eprom status register (estat) ?. 6 ccie command complete interrupt enable ?the ccie bit enables the interrupts in case of all commands being completed in the eeprom. 0 command complete interrupts disabled. 1 an interrupt will be requested whenever the ccif ?g is set (see section 3.3.2.6, ?eprom status register (estat) ?. 76543210 r epopen nv6 nv5 nv4 epdis ep2 ep1 ep0 w reset f fffffff = unimplemented or reserved figure 3-8. eeprom protection register (eprot) chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 124 freescale semiconductor to change the eeprom protection that will be loaded on reset, the upper sector of eeprom must ?st be unprotected, then the eeprom protect byte located at address 0x07fd must be written to. a protected eeprom sector is disabled by the epdis bit while the size of the protected sector is de?ed by the ep bits in the eprot register. trying to alter any of the protected areas will result in a protect violation error and pviol ?g will be set in the estat register. a mass erase of a whole eeprom block is only possible when protection is fully disabled by setting the epopen and epdis bits. an attempt to mass erase an eeprom block while protection is enabled will set the pviol ?g in the estat register. 3.3.2.6 eeprom status register (estat) the estat register de?es the eeprom state machine command status and eeprom array access, protection and erase verify status. table 3-5. eprot field descriptions field description 7 epopen opens eeprom for program or erase 0 the whole eeprom array is protected. in this case, the epdis and ep bits within the protection register are ignored. 1 the eeprom sectors not protected are enabled for program or erase. 6:4 nv[6:4] nonvolatile flag bits ?these three bits are available to the user as nonvolatile ?gs. 3 epdis eeprom protection address range disable the epdis bit determines whether there is a protected area in the space of the eeprom address map. 0 protection enabled 1 protection disabled 2:0 ep[2:0] eeprom protection address size ?the ep[2:0] bits determine the size of the protected sector. refer to table 3-6 . table 3-6. eeprom address range protection ep[2:0] protected address range protected size 000 0x07c0-0x07ff 64 bytes 001 0x0780-0x07ff 128 bytes 010 0x0740-0x07ff 192 bytes 011 0x0700-0x07ff 256 bytes 100 0x06c0-0x07ff 320 bytes 101 0x0680-0x07ff 384 bytes 110 0x0640-0x07ff 448 bytes 111 0x0600-0x07ff 512 bytes chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 125 cbeif, pviol, and accerr bits are readable and writable, ccif and blank bits are readable but not writable, remaining bits read 0 and are not writable in normal mode. fail is readable and writable in special mode. fail must be clear when starting a command write sequence. done is readable but not writable in special mode. 76543210 r cbeif ccif pviol accerr 0 blank 0 0 w reset 1 1 0 00000 = unimplemented or reserved figure 3-9. eeprom status register (estat - normal mode) 76543210 r cbeif ccif pviol accerr 0 blank fail done w reset 1 1 0 00001 = unimplemented or reserved figure 3-10. eeprom status register (estat - special mode) table 3-7. estat field descriptions field description 7 cbeif command buffer empty interrupt flag ?the cbeif ?g indicates that the address, data, and command buffers are empty so that a new command sequence can be started. the cbeif ?g is cleared by writing a 1 to cbeif. writing a 0 to the cbeif ?g has no effect on cbeif. writing a 0 to cbeif after writing an aligned word to the eeprom address space but before cbeif is cleared will abort a command sequence and cause the accerr ?g in the estat register to be set. writing a 0 to cbeif outside of a command sequence will not set the accerr ?g. the cbeif ?g is used together with the cbeie bit in the ecnfg register to generate an interrupt request. 0 buffers are full 1 buffers are ready to accept a new command 6 ccif command complete interrupt flag the ccif ?g indicates that there are no more commands pending. the ccif ?g is cleared when cbeif is cleared and sets automatically upon completion of all active and pending commands. the ccif ?g does not set when an active command completes and a pending command is fetched from the command buffer. writing to the ccif ?g has no effect. the ccif ?g is used together with the ccie bit in the ecnfg register to generate an interrupt request. 0 command in progress 1 all commands are completed 5 pviol protection violation ?the pviol ?g indicates an attempt was made to program or erase an address in a protected eeprom memory area ( section 3.4.1.4, ?llegal eeprom operations? . the pviol ?g is cleared by writing a 1 to pviol. writing a 0 to the pviol ?g has no effect on pviol. while pviol is set, it is not possible to launch another command in the eeprom. 0 no failure 1 a protection violation has occurred chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 126 freescale semiconductor 3.3.2.7 eeprom command register (ecmd) the ecmd register defines the eeprom commands. cmdb6, cmdb5, cmdb2, and cmdb0 bits are readable and writable during a command sequence while bits 7, 4, 3, and 1 read 0 and are not writable. 4 accerr eeprom access error ?the accerr ?g indicates an illegal access to the selected eeprom array ( section 3.4.1.4, ?llegal eeprom operations ). this can be either a violation of the command sequence, issuing an illegal command (illegal combination of the cmdbx bits in the ecmd register) or the execution of a cpu stop instruction while a command is executing (ccif = 0). the accerr ?g is cleared by writing a 1 to accerr. writing a 0 to the accerr ?g has no effect on accerr. while accerr is set, it is not possible to launch another command in the eeprom. 0 no failure 1 access error has occurred 2 blank array has been veri?d as erased ?the blank ?g indicates that an erase verify command has checked the eeprom array and found it to be erased. the blank ?g is cleared by hardware when cbeif is cleared as part of a new valid command sequence. writing to the blank ?g has no effect on blank. 0 if an erase verify command has been requested and the ccif ?g is set, then a 0 in blank indicates array is not erased 1 eeprom array veri?s as erased 1 fail flag indicating a failed eeprom operation ?the fail ?g will set if the erase verify operation fails (eeprom block veri?d as not erased). the fail ?g is cleared writing a 1 to fail. writing a 0 to the fail ?g has no effect on fail. 0 eeprom operation completed without error 1 eeprom operation failed 0 done flag indicating a completed eeprom operation 0 eeprom operation is active (program, erase, erase verify) 1 eeprom operation not active 76543210 r0 cmdb6 cmdb5 00 cmdb2 0 cmdb0 w reset 0 0 0 00000 = unimplemented or reserved figure 3-11. eeprom command register (ecmd) table 3-8. ecmd field descriptions field description 6, 5, 2, 0 cmdb[6:5] cmdb2 cmdb0 eeprom command ?valid eeprom commands are shown in table 3-9 . any other command written than those mentioned in table 3-9 sets the accerr bit in the estat register. table 3-7. estat field descriptions (continued) field description chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 127 3.3.2.8 reserved3 this register is reserved for factory testing and is not accessible to the user. all bits read 0 and are not writable. 3.3.2.9 eeprom address register (eaddr) eaddrhi and eaddrlo are the eeprom address registers. in normal modes, all eaddrhi and eaddrlo bits read 0 and are not writable. in special modes, all eaddrhi and eaddrlo bits are readable and writable except eaddrhi[7:2] which are not writable and always read 0. table 3-9. valid eeprom command list command meaning 0x05 erase verify 0x20 word program 0x40 sector erase 0x41 mass erase 0x60 sector modify 76543210 r00000000 w reset 00000000 = unimplemented or reserved figure 3-12. reserved3 76543210 r000000 eabhi w reset 00000000 = unimplemented or reserved figure 3-13. eeprom address high register (eaddrhi) 76543210 r eablo w reset 00000000 figure 3-14. eeprom address low register (eaddrlo) chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 128 freescale semiconductor for sector erase, the mcu address bits ab[1:0] are ignored. for mass erase, any address within the block is valid to start the command. chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 129 3.3.2.10 eeprom data register (edata) edatahi and edatalo are the eeprom data registers. in normal modes, all edatahi and edatalo bits read 0 and are not writable. in special modes, all edatahi and edatalo bits are readable and writable. 3.4 functional description 3.4.1 program and erase operation write and read operations are both used for the program and erase algorithms described in this subsection. these algorithms are controlled by a state machine whose timebase, eeclk, is derived from the oscillator clock via a programmable divider. the command register as well as the associated address and data registers operate as a buffer and a register (2-stage fifo) so that a new command along with the necessary data and address can be stored to the buffer while the previous command is remains in progress. the pipelined operation allows a simpli?ation of command launching. buffer empty as well as command completion are signalled by ?gs in the eeprom status register. interrupts for the eeprom will be generated if enabled. the next four subsections describe: how to write the eclkdiv register. command write sequences used to program, erase, and verify the eeprom memory. valid eeprom commands. errors resulting from illegal eeprom operations. 3.4.1.1 writing the eclkdiv register prior to issuing any program or erase command, it is first necessary to write the eclkdiv register to divide the oscillator down to within 150 khz to 200 khz range. the program and erase timings are also a 76543210 r edhi w reset 00000000 figure 3-15. eeprom data high register (edatahi) 76543210 r edlo w reset 00000000 figure 3-16. eeprom data low register (edatalo) chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 130 freescale semiconductor function of the bus clock, such that the eclkdiv determination must take this information into account. if we define: eeclk as the clock of the eeprom timing control block tbus as the period of the bus clock int(x) as taking the integer part of x (e.g., int(4.323)=4), then eclkdiv register bits prdiv8 and ediv[5:0] are to be set as described in figure 3-17 . for example, if the oscillator clock is 950 khz and the bus clock is 10 mhz, eclkdiv bits ediv[5:0] must be set to 4 (binary 000100) and bit prdiv8 set to 0. the resulting eeclk is then 190 khz. as a result, the eeprom algorithm timings are increased over optimum target by: command execution time will increase proportionally with the period of eeclk. caution because of the impact of clock synchronization on the accuracy of the functional timings, programming or erasing the eeprom cannot be performed if the bus clock runs at less than 1 mhz. programming the eeprom with an oscillator clock < 150 khz must be avoided. setting eclkdiv to a value such that eeclk < 150 khz can reduce the lifetime of the eeprom due to overstress. setting eclkdiv to a value such that (1/eeclk+tbus) < 5 s can result in incomplete programming or erasure of the memory array cells. if the eclkdiv register is written, the bit edivld is set automatically. if this bit is 0, the register has not been written since the last reset. eeprom commands will not be executed if this register has not been written to. 200 190 () 200 ? 100 5% = chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 131 figure 3-17. prdiv8 and ediv bits determination procedure prdiv8 = 1 yes no prdiv8 = 0 (reset) eeclk = (prdclk)/(1+ediv[5:0]) prdclk = oscillator clock prdclk = oscillator clock/8 prdclk[mhz]*(5+tbus[ s]) no ediv[5:0] = prdclk[mhz]*(5+tbus[ s])-1 yes start tbus 1 s? an integer? ediv[5:0] = int(prdclk[mhz]*(5+tbus[ s])) 1/eeclk [mhz] + tbus[ms] 5 and eeclk > 0.15 mhz ? end yes no ediv[5:0] 4? program/erase impossible yes no program/erase impossible no try to decrease tbus yes oscillator clock > 12.8 mhz? chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 132 freescale semiconductor 3.4.1.2 command write sequence the eeprom command controller is used to supervise the command write sequence to execute program, erase, mass erase, sector modify, and erase verify operations. before starting a command write sequence, it is necessary to check that there is no pending access error or protection violation (the accerr and pviol ?gs must be cleared in the estat register). after this initial step, the cbeif ?g must be tested to ensure that the address, data and command buffers are empty. if so, the command sequence can be started. the following 3-step command write sequence must be strictly adhered to and no intermediate access to the eeprom array is permitted between the 3 steps. it is possible to read any eeprom register during a command sequence. the command write sequence is as follows: 1. write an aligned word to be to a valid eeprom array address. the address and data will be stored in internal buffers. for program and sector modify, all address and data bits are valid. for erase, the value of the data bytes are ignored. for mass erase and erase verify, the address can be anywhere in the available address space of the array. for sector erase, the address bits[1:0] are ignored. 2. write a valid command, listed in table 3-10 , to the ecmd register. 3. clear the cbeif ?g by writing a 1 to cbeif to launch the command. when the cbeif ?g is cleared, the ccif ?g is cleared by hardware indicating that the command was successfully launched. the cbeif ?g will be set again indicating the address, data, and command buffers are ready for a new command write sequence to begin. the completion of the command is indicated by the ccif ?g setting. the ccif ?g only sets when all active and pending commands have been completed. the eeprom command controller will ?g errors in command write sequences by means of the accerr (access error) and pviol (protection violation) ?gs in the estat register. an erroneous command write sequence will abort and set the appropriate ?g. if set, the user must clear the accerr or pviol ?gs before commencing another command write sequence. by writing a 0 to the cbeif ?g the command sequence can be aborted after the word write to the eeprom address space or after writing a command to the ecmd register and before the command is launched. writing a 0 to the cbeif ?g in this way will set the accerr ?g. a summary of the launching of a program operation is shown in figure 3-18 . for other operations, the user writes the appropriate command to the ecmd register. chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 133 figure 3-18. example program command flow write: register eclkdiv read: register eclkdiv bit edivld set? write: array address and write: register ecmd program command 0x20 write: register estat yes no clear bit cbeif 0x80 cbeif set? bit yes clock register written check 1. 2. 3. clear bit accerr 0x10 write: register estat no yes no protection violation check access error check read: register estat ccif set? bit no no address, data, command buffer empty check next write? yes exit no program data clear bit pviol 0x20 write: register estat yes pviol set? bit accerr set? bit bit polling for command completion check read: register estat yes note: command sequence aborted by writing 0x00 to estat register. note: command sequence aborted by writing 0x00 to estat register. chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 134 freescale semiconductor 3.4.1.3 valid eeprom commands table 3-10 summarizes the valid eeprom commands. also shown are the effects of the commands on the eeprom array. caution an eeprom word must be in an erased state before being programmed. cumulative programming of bits within a word is not allowed. the sector modify command (0x60) is a two-step command which first erases a sector (2 words) of the eeprom array and then re-programs one of the words in that sector. the eeprom sector which is erased by the sector modify command is the sector containing the address of the aligned array write which starts the valid command sequence. that same address is re-programmed with the data which is written. by launching a sector modify command and then pipelining a program command it is possible to completely replace the contents of an eeprom sector. 3.4.1.4 illegal eeprom operations the accerr flag will be set during the command write sequence if any of the following illegal operations are performed causing the command write sequence to immediately abort: 1. writing to the eeprom address space before initializing eclkdiv. 2. writing a misaligned word or a byte to the valid eeprom address space. 3. writing to the eeprom address space while cbeif is not set. 4. writing a second word to the eeprom address space before executing a program or erase command on the previously written word. 5. writing to any eeprom register other than ecmd after writing a word to the eeprom address space. 6. writing a second command to the ecmd register before executing the previously written command. 7. writing an invalid command to the ecmd register in normal mode. 8. writing to any eeprom register other than estat (to clear cbeif) after writing to the command register (ecmd). table 3-10. valid eeprom commands ecmd meaning function on eeprom array 0x05 erase verify verify all memory bytes of the eeprom array are erased. if the array is erased, the blank bit will set in the estat register upon command completion. 0x20 program program a word (two bytes). 0x40 sector erase erase two words (four bytes) of eeprom array. 0x41 mass erase erase all of the eeprom array. a mass erase of the full array is only possible when epdis and epopen are set. 0x60 sector modify erase two words of eeprom, re-program one word. chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 135 9. the part enters stop mode and a program or erase command is in progress. the command is aborted and any pending command is killed. 10. a 0 is written to the cbeif bit in the estat register. the accerr flag will not be set if any eeprom register is read during the command sequence. if the eeprom array is read during execution of an algorithm (i.e., ccif bit in the estat register is low), the read will return non-valid data and the accerr flag will not be set. when an accerr flag is set in the estat register, the command state machine is locked. it is not possible to launch another command until the accerr flag is cleared. the pviol flag will be set during the command write sequence after the word write to the eeprom address space and the command sequence will be aborted if any of the following illegal operations are performed. 1. writing a eeprom address to program in a protected area of the eeprom. 2. writing a eeprom address to erase in a protected area of the eeprom. 3. writing the mass erase command to ecmd while any protection is enabled. when the pviol flag is set in the estat register the command state machine is locked. it is not possible to launch another command until the pviol flag is cleared. 3.5 operating modes 3.5.1 wait mode if an eeprom command is active (ccif = 0) when the mcu enters wait mode, that command and any pending command will be completed. the eets2k module can recover the mcu from wait mode if the interrupts are enabled (see section 3.7, ?nterrupts ). 3.5.2 stop mode if a command is active (ccif = 0) when the mcu enters stop mode, the operation will be aborted and if the operation is program, erase, or sector modify, the data being programmed or erased may be corrupted and the ccif and accerr flags will be set. if active, the high voltage circuitry to the eeprom array will be switched off when entering stop mode. upon exit from stop mode, the cbeif flag is set and any pending command will not be launched. the accerr flag must be cleared before starting a new command write sequence. note as active commands are immediately aborted when the mcu enters stop mode, it is strongly recommended that the user does not use the stop instruction during program, erase, or sector modify operations. chapter 3 2 kbyte eeprom module (eets2kv1) mc9s12kg128 data sheet, rev. 1.15 136 freescale semiconductor 3.5.3 background debug mode in background debug mode (bdm), the eprot register is writable. if the chip is unsecured then all eeprom commands listed in table 3-10 can be executed. if the chip is secured in special single-chip mode, then the only possible command to execute is mass erase. 3.6 resets if a reset occurs while any eeprom command is in progress, that command will be immediately aborted. the state of the word being programmed or the sector / block being erased is not guaranteed. 3.7 interrupts the eeprom module can generate an interrupt when all eeprom commands are completed or the address, data, and command buffers are empty. note vector addresses and their relative interrupt priority are determined at the mcu level. for a detailed description of the register bits, refer to section 3.3.2.4, ?eprom configuration register (ecnfg) and section 3.3.2.6, ?eprom status register (estat) . table 3-11. eeprom interrupt sources interrupt source interrupt flag local enable global (ccr) mask eeprom address, data and command buffers empty cbeif (estat register) cbeie i bit all commands are completed on eeprom ccif (estat register) ccie i bit mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 137 chapter 4 port integration module (pim9kg128v1) 4.1 introduction the port integration module (pim) establishes the interface between the peripheral modules and the i/o pins for ports h, j, m, p, s and t. this section covers: port h associated with the two spi modules ?spi1 and spi2. these ports can also be used as external interrupt sources. port j associated with 1 iic module and the can4 module, which can also be used as an external interrupt source port m associated with 2 can modules can0 and can4, the spi module associated with port s port p connected to either the pwm or the two spi modules associated with port h, which also can be used as an external interrupt source port s associated with 2 sci and 1 spi module port t connected to tim module each i/o pin can be con?ured by several registers in order to select data direction and drive strength, to enable and select pull-up or pull-down resistors. on certain pins also interrupts can be enabled which result in status ?gs. the i/o s of 2 can and all 3 spi modules can be routed from their default location to determined pins. 4.1.1 features a standard port has the following minimum features: input/output selection 3.3v/5v output drive with two selectable drive strength 3.3v/5v digital and analog input input with selectable pull-up or pull-down device optional features: open drain for wired-or connections interrupt inputs with glitch ?tering chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 138 freescale semiconductor 4.1.2 block diagram figure 4-1 is a block diagram of the pim9kg128. figure 4-1. pim9kg128 block diagram port t pt0 pt1 pt2 pt3 pt4 pt5 pt6 pt7 tim ioc0 ioc1 ioc2 ioc3 ioc4 ioc5 ioc6 ioc7 port p pp0 pp1 pp2 pp3 pp4 pp5 pp6 pp7 pwm pw0 pw1 pw2 pw3 pw4 pw5 pw6 pw7 port s ps0 ps1 ps2 ps3 ps4 ps5 ps6 ps7 rxd txd rxd txd sdi/miso sdo/mosi sck ss sci0 sci1 spi0 port h ph0 ph1 ph2 ph3 ph4 ph5 ph6 ph7 port j pj0 pj1 pj6 pj7 port m pm0 pm1 pm2 pm3 pm4 pm5 pm6 pm7 port integration module ip-bus intj inth intp kwp0 kwp1 kwp2 kwp3 kwp4 kwp5 kwp6 kwp7 kwh0 kwh1 kwh2 kwh3 kwh4 kwh5 kwh6 kwh7 sdi/miso sdo/mosi sck ss spi1 sdi/miso sdo/mosi sck ss spi2 module to port routing rxcan txcan can0 rxcan txcan can4 sda scl iic kwj0 kwj1 kww6 kww7 chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 139 4.2 external signal description this section lists and describes the signals that do connect off chip. 4.2.1 signal properties table 4-1 shows all the pins and their functions that are controlled by the pim9kg128. if there is more than one function associated with a pin, the priority is indicated by the position in the table from top (highest priority) to down (lowest priority). all pins have reset state as input. table 4-1. pin functions and priorities (sheet 1 of 4) port pin name pin function and priority description pull mode after reset pin function after reset port t pt[7:0] ioc[7:0] timer channels 7 to 0 hi-z gpio gpio general-purpose i/o port s ps7 ss0 serial peripheral interface 0 slave select output in master mode, input in slave mode or master mode. pull-up gpio gpio general-purpose i/o ps6 sck0 serial peripheral interface 0 serial clock pin gpio general-purpose i/o ps5 mosi0 serial peripheral interface 0 master out/slave in pin gpio general-purpose i/o ps4 miso0 serial peripheral interface 0 master in/slave out pin gpio general-purpose i/o ps3 txd1 serial communication interface 1 transmit pin gpio general-purpose i/o ps2 rxd1 serial communication interface 1 receive pin gpio general-purpose i/o ps1 txd0 serial communication interface 0 transmit pin gpio general-purpose i/o ps0 rxd0 serial communication interface 0 receive pin gpio general-purpose i/o chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 140 freescale semiconductor port m pm7 txcan4 mscan4 transmit pin hi-z gpio gpio general-purpose i/o pm6 rxcan4 mscan4 receive pin gpio general-purpose i/o pm5 txcan0 mscan0 transmit pin txcan4 mscan4 transmit pin sck0 serial peripheral interface 0 serial clock pin gpio general-purpose i/o pm4 rxcan0 mscan0 receive pin rxcan4 mscan4 receive pin mosi0 serial peripheral interface 0 master out/slave in pin gpio general-purpose i/o pm3 txcan0 mscan0 transmit pin ss0 1 serial peripheral interface 0 slave select output in master mode, input for slave mode or master mode. gpio general-purpose i/o pm2 rxcan0 mscan0 receive pin miso0 1 serial peripheral interface 0 master in/slave out pin gpio general-purpose i/o pm1 txcan0 mscan0 transmit pin gpio general-purpose i/o pm0 rxcan0 mscan0 receive pin gpio general-purpose i/o table 4-1. pin functions and priorities (sheet 2 of 4) port pin name pin function and priority description pull mode after reset pin function after reset chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 141 port p pp7 pwm7 pulse width modulator channel 7 hi-z gpio sck2 serial peripheral interface 2 serial clock pin gpio/kwp7 general-purpose i/o with interrupt pp6 pwm6 pulse width modulator channel 6 ss2 serial peripheral interface 2 slave select output in master mode, input in slave mode or master mode. gpio/kwp6 general-purpose i/o with interrupt pp5 pwm5 pulse width modulator channel 5 mosi2 serial peripheral interface 2 master out/slave in pin gpio/kwp5 general-purpose i/o with interrupt pp4 pwm4 pulse width modulator channel 4 miso2 serial peripheral interface 2 master in/slave out pin gpio/kwp4 general-purpose i/o with interrupt pp3 pwm3 pulse width modulator channel 3 ss1 serial peripheral interface 1 slave select output in master mode, input in slave mode or master mode. gpio/kwp3 general-purpose i/o with interrupt pp2 pwm2 pulse width modulator channel 2 sck1 serial peripheral interface 1 serial clock pin gpio/kwp2 general-purpose i/o with interrupt pp1 pwm1 pulse width modulator channel 1 mosi1 serial peripheral interface 1 master out/slave in pin gpio/kwp1 general-purpose i/o with interrupt pp0 pwm0 pulse width modulator channel 0 miso1 serial peripheral interface 1 master in/slave out pin gpio/kwp0 general-purpose i/o with interrupt table 4-1. pin functions and priorities (sheet 3 of 4) port pin name pin function and priority description pull mode after reset pin function after reset chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 142 freescale semiconductor port h ph7 ss2 serial peripheral interface 2 slave select output in master mode, input in slave mode or master mode. hi-z gpio gpio/kwh7 general-purpose i/o with interrupt ph6 sck2 serial peripheral interface 2 serial clock pin gpio/kwh6 general-purpose i/o with interrupt ph5 mosi2 serial peripheral interface 2 master out/slave in pin gpio/kwh5 general-purpose i/o with interrupt ph4 miso2 serial peripheral interface 2 master in/slave out pin gpio/kwh4 general-purpose i/o with interrupt ph3 ss1 serial peripheral interface 1 slave select output in master mode, input in slave mode or master mode. gpio/kwh3 general-purpose i/o with interrupt ph2 sck1 serial peripheral interface 1 serial clock pin gpio/kwh2 general-purpose i/o with interrupt ph1 mosi1 serial peripheral interface 1 master out/slave in pin gpio/kwh1 general-purpose i/o with interrupt ph0 miso1 serial peripheral interface 1 master in/slave out pin gpio/kwh0 general-purpose i/o with interrupt port j pj7 txcan4 mscan4 transmit pin pull-up gpio scl inter integrated circuit serial clock line gpio/kwj7 general-purpose i/o with interrupt pj6 rxcan4 mscan4 receive pin sda inter integrated circuit serial data line gpio/kwj6 general-purpose i/o with interrupt pj1 gpio/kwj1 general-purpose i/o with interrupt pj0 gpio/kwj0 general-purpose i/o with interrupt 1 if can0 is routed to pm[3:2] the spi0 can still be used in bidirectional master mode. table 4-1. pin functions and priorities (sheet 4 of 4) port pin name pin function and priority description pull mode after reset pin function after reset chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 143 4.3 memory map and register de?ition this section provides a detailed description of all registers. table 4-2 is a standard memory map of pim9kg128. table 4-2. pim9kg128 memory map address offset use access 0x0000 port t i/o register (ptt) r/w 0x0001 port t input register (ptit) r 0x0002 port t data direction register (ddrt) r/w 0x0003 port t reduced drive register (rdrt) r/w 0x0004 port t pull device enable register (pert) r/w 0x0005 port t polarity select register (ppst) r/w 0x0006 - 0x0007 reserved 0x0008 port s i/o register (pts) r/w 0x0009 port s input register (ptis) r 0x000a port s data direction register (ddrs) r/w 0x000b port s reduced drive register (rdrs) r/w 0x000c port s pull device enable register (pers) r/w 0x000d port s polarity select register (ppss) r/w 0x000e port s wired-or mode register (woms) r/w 0x000f reserved 0x0010 port m i/o register (ptm) r/w 0x0011 port m input register (ptim) r 0x0012 port m data direction register (ddrm) r/w 0x0013 port m reduced drive register (rdrm) r/w 0x0014 port m pull device enable register (perm) r/w 0x0015 port m polarity select register (ppsm) r/w 0x0016 port m wired-or mode register (womm) r/w 0x0017 port m module routing register (modrr) r/w 0x0018 port p i/o register (ptp) r/w 0x0019 port p input register (ptip) r 0x001a port p data direction register (ddrp) r/w 0x001b port p reduced drive register (rdrp) r/w 0x001c port p pull device enable register (perp) r/w 0x001d port p polarity select register (ppsp) r/w 0x001e port p interrupt enable register (piep) r/w 0x001f port p interrupt flag register (pifp) r/w chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 144 freescale semiconductor 0x0020 port h i/o register (pth) r/w 0x0021 port h input register (ptih) r 0x0022 port h data direction register (ddrh) r/w 0x0023 port h reduced drive register (rdrh) r/w 0x0024 port h pull device enable register (perh) r/w 0x0025 port h polarity select register (ppsh) r/w 0x0026 port h interrupt enable register (pieh) r/w 0x0027 port h interrupt flag register (pifh) r/w 0x0028 port j i/o register (ptj) r/w 0x0029 port j input register (ptij) r 0x002a port j data direction register (ddrj) r/w 0x002b port j reduced drive register (rdrj) r/w 0x002c port j pull device enable register (perj) r/w 0x002d port j polarity select register (ppsj) r/w 0x002e port j interrupt enable register (piej) r/w 0x002f port j interrupt flag register (pifj) r/w 0x0030 - 0x003f reserved table 4-2. pim9kg128 memory map (continued) address offset use access chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 145 4.3.1 port t registers port t is associated with the 8-channel timer (tim). each pin is assigned to these modules according to the following priority: timer > general-purpose i/o. if the timer is enabled, the timer channels configured for output compare are available on port t pins pt[7:0]. refer to the tim block description chapter for information on enabling and disabling the tim module. during reset, port t pins are con?ured as high-impedance inputs. 4.3.1.1 port t i/o register (ptt) read: anytime. write: anytime. if the data direction bits of the associated i/o pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. 4.3.1.2 port t input register (ptit) read: anytime. write: never, writes to this register have no effect. this register always reads back the status of the associated pins. module base + 0x0000 76543210 r ptt7 ptt6 ptt5 ptt4 ptt3 ptt2 ptt1 ptt0 w timer ioc7 ioc6 ioc5 ioc4 ioc3 ioc2 ioc1 ioc0 reset 0 0 0 00000 figure 4-2. port t i/o register (ptt)) module base + 0x0001 76543210 r ptit7 ptit6 ptit5 ptit4 ptit3 ptit2 ptit1 ptit0 w reset u u u uuuuu = reserved or unimplemented u = unaffected by reset figure 4-3. port t input register (ptit) chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 146 freescale semiconductor 4.3.1.3 port t data direction register (ddrt) read: anytime. write: anytime. this register con?ures each port t pin as either input or output. the tim forces the i/o state to be an output for each timer port associated with an enabled output compare. in these cases the data direction bits will not change. the ddrt bits revert to controlling the i/o direction of a pin when the associated timer output compare is disabled. the timer input capture always monitors the state of the pin. 4.3.1.4 port t reduced drive register (rdrt) read: anytime. write: anytime. this register con?ures the drive strength of each port t output pin as either full or reduced. if the port is used as input this bit is ignored. module base + 0x0002 76543210 r ddrt7 ddrt6 ddrt5 ddrt4 ddrt3 ddrt2 ddrt1 ddrt0 w reset 0 0 0 00000 figure 4-4. port t data direction register (ddrt) table 4-3. ddrt field descriptions field description 7? ddrt[7:0] data direction port t 0 associated pin is con?ured as input. 1 associated pin is con?ured as output. module base + 0x0003 76543210 r rdrt7 rdrt6 rdrt5 rdrt4 rdrt3 rdrt2 rdrt1 rdrt0 w reset 0 0 0 00000 figure 4-5. port t reduced drive register (rdrt) table 4-4. rdrt field descriptions field description 7? rdrt[7:0] reduced drive port t 0 full drive strength at output. 1 associated pin drives at about 1/6 of the full drive strength. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 147 4.3.1.5 port t pull device enable register (pert) read: anytime. write: anytime. this register con?ures whether a pull-up or a pull-down device is activated, if the port is used as input. this bit has no effect if the port is used as output. out of reset no pull device is enabled. 4.3.1.6 port t polarity select register (ppst) read: anytime. write: anytime. this register selects whether a pull-down or a pull-up device is connected to the pin. module base + 0x0004 76543210 r pert7 pert6 pert5 pert4 pert3 pert2 pert1 pert0 w reset 0 0 0 00000 figure 4-6. port t pull device enable register (pert) table 4-5. pert field descriptions field description 7? pert[7:0] pull device enable port t 0 pull-up or pull-down device is disabled. 1 either a pull-up or pull-down device is enabled. module base + 0x0005 76543210 r ppst7 ppst6 ppst5 ppst4 ppst3 ppst2 ppst1 ppst0 w reset 0 0 0 00000 figure 4-7. port t polarity select register (ppst) table 4-6. ppst field descriptions field description 7? ppst[7:0] pull select port t 0 a pull-up device is connected to the associated port t pin, if enabled by the associated bit in register pert and if the port is used as input. 1 a pull-down device is connected to the associated port t pin, if enabled by the associated bit in register pert and if the port is used as input. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 148 freescale semiconductor 4.3.2 port s registers port s is associated with the serial peripheral interface (spi0) and serial communication interfaces (sci1, sci0). each pin is assigned to these modules according to the following priority: spi0/sci1/sci0 > general-purpose i/o. when the spi0 is enabled, the ps[7:4] pins become ss0, sck0, mosi0, and miso0 respectively. refer to the spi block description chapter for information on enabling and disabling the spi0. the spi0 pins can be re-routed. refer to section 4.3.3.8, ?odule routing register (modrr)? when the sci1 receiver and transmitter are enabled, the ps[3:2] pins become txd1 and rxd1 respectively. when the sci0 receiver and transmitter are enabled, the ps[1:0] pins become txd0 and rxd0 respectively. refer to the sci block description chapter for information on enabling and disabling the sci receiver and transmitter. during reset, port s pins are con?ured as inputs with pull-up. 4.3.2.1 port s i/o register (pts) read: anytime. write: anytime. if the data direction bits of the associated i/o pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. the spi0 function takes precedence over the general-purpose i/o function if the spi0 is enabled. if enabled, the sci0(1) transmitter takes precedence over the general-purpose i/o function, and the corresponding txd0(1) pin is configured as an output. if enabled, the sci0(1) receiver takes precedence over the general-purpose i/o function, and the corresponding rxd0(1) pin is configured as an input. module base + 0x0008 76543210 r pts7 pts6 pts5 pts4 pts3 pts2 pts1 pts0 w spi/sci ss0 sck0 mosi0 miso0 txd1 rxd1 txd0 rxd0 reset 0 0 0 00000 figure 4-8. port s i/o register (pts) chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 149 4.3.2.2 port s input register (ptis) read: anytime. write: never, writes to this register have no effect. this register always reads back the status of the associated pins. 4.3.2.3 port s data direction register (ddrs) read: anytime. write: anytime. this register con?ures each port s pin as either input or output. when the spi0 is enabled, the ps[7:4] pins become the spi bidirectional pins. the associated data direction register bits have no effect. when the sci0(1) transmitter is enabled, the ps[1](ps[3]) pin becomes the txd0(1) output pin and the associated data direction register bit has no effect. when the sci0(1) receiver is enabled, the ps[0](ps[2]) pin becomes the rxd0(1) input pin and the associated data direction register bit has no effect. if the spi0, sci0 and sci1 functions are disabled, the corresponding data direction register bit reverts to control the i/o direction of the associated pin. module base + 0x0009 76543210 r ptis7 ptis6 ptis5 ptis4 ptis3 ptis2 ptis1 ptis0 w reset u u u uuuuu = reserved or unimplemented u = unaffected by reset figure 4-9. port s input register (ptis) module base + 0x000a 76543210 r ddrs7 ddrs6 ddrs5 ddrs4 ddrs3 ddrs2 ddrs1 ddrs0 w reset 0 0 0 00000 figure 4-10. port s data direction register (ddrs) table 4-7. ddrs field descriptions field description 7? ddrs[7:0] data direction port s 0 associated pin is con?ured as input. 1 associated pin is con?ured as output. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 150 freescale semiconductor 4.3.2.4 port s reduced drive register (rdrs) read: anytime. write: anytime. this register con?ures the drive strength of each port s output pin as either full or reduced. if the port is used as input this bit is ignored. 4.3.2.5 port s pull device enable register (pers) read: anytime. write: anytime. this register con?ures whether a pull-up or a pull-down device is activated, if the port is used as input or as output in wired-or (open drain) mode. this bit has no effect if the port is used as push-pull output. out of reset a pull-up device is enabled. module base + 0x000b 76543210 r rdrs7 rdrs6 rdrs5 rdrs4 rdrs3 rdrs2 rdrs1 rdrs0 w reset 0 0 0 00000 figure 4-11. port s reduced drive register (rdrs) table 4-8. rdrs field descriptions field description 7? rdrs[7:0] reduced drive port s 0 full drive strength at output. 1 associated pin drives at about 1/6 of the full drive strength. module base + 0x000c 76543210 r pers7 pers6 pers5 pers4 pers3 pers2 pers1 pers0 w reset 1 1 1 11111 figure 4-12. port s pull device enable register (pers) table 4-9. pers field descriptions field description 7? pers[7:] pull device enable port s 0 pull-up or pull-down device is disabled. 1 either a pull-up or pull-down device is enabled. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 151 4.3.2.6 port s polarity select register (ppss) read: anytime. write: anytime. this register selects whether a pull-down or a pull-up device is connected to the pin. 4.3.2.7 port s wired-or mode register (woms) read: anytime. write: anytime. this register con?ures the output pins as wired-or. if enabled the output is driven active low only (open-drain). a logic level of ??is not driven. it applies also to the spi and sci outputs and allows a multipoint connection of several serial modules. this bit has no in?ence on pins used as inputs. module base + 0x000d 76543210 r ppss7 ppss6 ppss5 ppss4 ppss3 ppss2 ppss1 ppss0 w reset 0 0 0 00000 figure 4-13. port s polarity select register (ppss) table 4-10. ppss field descriptions field description 7? ppss[7:0] pull select port s 0 a pull-up device is connected to the associated port s pin, if enabled by the associated bit in register pers and if the port is used as input or as wired-or output. 1 a pull-down device is connected to the associated port s pin, if enabled by the associated bit in register pers and if the port is used as input. module base + 0x000e 76543210 r woms7 woms6 woms5 woms4 woms3 woms2 woms1 woms0 w reset 0 0 0 00000 figure 4-14. port s wired-or mode register (woms) table 4-11. woms field descriptions field description 7? woms[7:0] wired-or mode port s 0 output buffers operate as push-pull outputs. 1 output buffers operate as open-drain outputs. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 152 freescale semiconductor 4.3.3 port m registers port m is associated with two freescale? scalable controller area network (can4, can0) and one serial peripheral interface (spi0) modules. each pin is assigned to these modules according to the following priority: can0 > can4 > spi0 > general-purpose i/o. refer to the spi block description chapter for information on enabling and disabling the spi0. refer to the mscan block description chapter for information on enabling and disabling can0 or can4 . the spi0, can0 and can4 pins can be re-routed. refer to section 4.3.3.8, ?odule routing register (modrr)? during reset, port m pins are con?ured as high-impedance inputs. 4.3.3.1 port m i/o register (ptm) read: anytime. write: anytime. if the data direction bits of the associated i/o pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. 4.3.3.2 port m input register (ptim) read: anytime. write: never, writes to this register have no effect. this register always reads back the status of the associated pins. module base + 0x0010 76543210 r ptm7 ptm6 ptm5 ptm4 ptm3 ptm2 ptm1 ptm0 w spi0 sck0 mosi0 ss0 miso0 can4 txcan4 rxcan4 txcan4 rxcan4 can0 txcan0 rxcan0 txcan0 rxcan0 txcan0 rxcan0 reset 0 0 0 00000 figure 4-15. port m i/o register (ptm) module base + 0x0011 76543210 r ptim7 ptim6 ptim5 ptim4 ptim3 ptim2 ptim1 ptim0 w reset u u u uuuuu = reserved or unimplemented u = unaffected by reset figure 4-16. port m input register (ptim) chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 153 4.3.3.3 port m data direction register (ddrm) read: anytime. write: anytime. this register con?ures each port m pin as either input or output. the can forces the i/o state to be an output for each port line associated with an enabled output (txcan4 and txcan0). it also forces the i/o state to be an input for each port line associated with an enabled input (rxcan4 and rxcan0). in those cases the data direction bits will not change. the ddrm bits revert to controlling the i/o direction of a pin when the associated peripheral module is disabled. 4.3.3.4 port m reduced drive register (rdrm) read: anytime. write: anytime. this register con?ures the drive strength of each port m output pin as either full or reduced. if the port is used as input this bit is ignored. module base + 0x0012 76543210 r ddrm7 ddrm6 ddrm5 ddrm4 ddrm3 ddrm2 ddrm1 ddrm0 w reset 0 0 0 00000 figure 4-17. port m data direction register (ddrm) table 4-12. ddrm field descriptions field description 7? ddrm[7:0] data direction port m 0 associated pin is con?ured as input. 1 associated pin is con?ured as output. module base + 0x0013 76543210 r rdrm7 rdrm6 rdrm5 rdrm4 rdrm3 rdrm2 rdrm1 rdrm0 w reset 0 0 0 00000 figure 4-18. port m reduced drive register (rdrm) table 4-13. rdrm field descriptions field description 7? rdrm[7:0] reduced drive port m 0 full drive strength at output. 1 associated pin drives at about 1/6 of the full drive strength. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 154 freescale semiconductor 4.3.3.5 port m pull device enable register (perm) read: anytime. write: anytime. this register con?ures whether a pull-up or a pull-down device is activated, if the port is used as input or wired-or output. this bit has no effect if the port is used as push-pull output. out of reset no pull device is enabled. 4.3.3.6 port m polarity select register (ppsm) read: anytime. write: anytime. this register selects whether a pull-down or a pull-up device is connected to the pin. if can is active a pull-up device can be activated on the receiver inputs, but not a pull-down. module base + 0x0014 76543210 r perm7 perm6 perm5 perm4 perm3 perm2 perm1 perm0 w reset 0 0 0 00000 figure 4-19. port m pull device enable register (perm) table 4-14. perm field descriptions field description 7? perm[7:0] pull device enable port m 0 pull-up or pull-down device is disabled. 1 either a pull-up or pull-down device is enabled. module base + 0x0015 76543210 r ppsm7 ppsm6 ppsm5 ppsm4 ppsm3 ppsm2 ppsm1 ppsm0 w reset 0 0 0 00000 figure 4-20. port m polarity select register (ppsm) table 4-15. ppsm field descriptions field description 7? ppsm[7:0] pull select port m 0 a pull-up device is connected to the associated port m pin, if enabled by the associated bit in register perm and if the port is used as general purpose, rxcan input. 1 a pull-down device is connected to the associated port m pin, if enabled by the associated bit in register perm and if the port is used as a general purpose but not as rxcan. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 155 4.3.3.7 port m wired-or mode register (womm) read: anytime. write: anytime. this register con?ures the output pins as wired-or. if enabled the output is driven active low only (open-drain). a logic level of ? is not driven. it applies also to the can outputs and allows a multipoint connection of several serial modules. this bit has no in?ence on pins used as inputs. 4.3.3.8 module routing register (modrr) read: anytime. write: anytime. this register con?ures the re-routing of can0, can4, spi0, spi1 and spi2 on de?ed port pins. module base + 0x0016 76543210 r womm7 womm6 womm5 womm4 womm3 womm2 womm1 womm0 w reset 0 0 0 00000 figure 4-21. port m wired-or mode register (womm) table 4-16. womm field descriptions field description 7? womm[7:0] wired-or mode port m 0 output buffers operate as push-pull outputs. 1 output buffers operate as open-drain outputs. module base + 0x0017 76543210 r0 modrr6 modrr5 modrr4 modrr3 modrr2 modrr1 modrr0 w reset 0 0 0 00000 = unimplemented or reserved figure 4-22. module routing register (modrr) table 4-17. modrr field descriptions field description 6 modrr6 spi2 routing bit ?see table 4-22 . 5 modrr5 spi1 routing bit ?see table 4-21 . 4 modrr4 spi0 routing bit ?see table 4-20 . chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 156 freescale semiconductor 3? modrr[3:2] can4 routing bits ?see table 4-19 . 1? modrr[1:0] can0 routing bits ?see table 4-18 . table 4-18. can0 routing modrr[1] modrr[0] rxcan0 txcan0 0 0 pm0 pm1 0 1 pm2 pm3 1 0 pm4 pm5 1 1 reserved table 4-19. can4 routing modrr[3] modrr[2] rxcan4 txcan4 0 0 pj6 pj7 0 1 pm4 pm5 1 0 pm6 pm7 1 1 reserved table 4-20. spi0 routing modrr[4] miso0 mosi0 sck0 ss0 0 ps4 ps5 ps6 ps7 1 pm2 pm4 pm5 pm3 table 4-21. spi1 routing modrr[5] miso1 mosi1 sck1 ss1 0 pp0 pp1 pp2 pp3 1 ph0 ph1 ph2 ph3 table 4-22. spi2 routing modrr[6] miso2 mosi2 sck2 ss2 0 pp4 pp5 pp6 pp7 1 ph4 ph5 ph6 ph7 table 4-17. modrr field descriptions (continued) field description chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 157 if the spi0 module is routed on pm[5:4] and used in bidirectional master mode with disabled ss output, pm[3:2] are free to be used with can or gpio. table 4-23. implemented modules on derivatives number of modules mscan modules spi modules can0 can4 spi0 spi1 spi2 3xxxxx 2xxxx 1x x chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 158 freescale semiconductor 4.3.4 port p registers port p is associated with the pulse width modulator (pwm) and two serial peripheral interfaces (spi1, spi2). each pin is assigned to these modules according to the following priority: pwm > spi2/sp1 > general-purpose i/o. when a pwm channel is enabled, the corresponding pin becomes a pwm output with the exception of of pin 7 which can be pwm input or output. refer to the pwm block description chapter for information on enabling and disabling the pwm channels. when spi2 is enabled and the corresponding pwm channels are disabled, the respective pin configuration for pp[7:4] is determined by several status bits in the spi2 module. when spi1 is enabled and the corresponding pwm channels are disabled, the respective pin configuration for pp[3:0] is determined by several status bits in the spi1 module. refer to the spi block description chapter for information on enabling and disabling the spi. the spi1 and spi2 pins can be re-routed. refer to section 4.3.3.8, ?odule routing register (modrr) . during reset, port p pins are con?ured as high-impedance inputs. 4.3.4.1 port p i/o register (ptp) read: anytime. write: anytime. if the data direction bits of the associated i/o pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. the pwm function takes precedence over the general purpose i/o function if the associated pwm channel is enabled. while channels 6-0 are output only if the respective channel is enabled, channel 7 can be pwm output or input if the shutdown feature is enabled. the spi function takes precedence over the general purpose i/o function associated with if enabled. if both pwm and spi are enabled the pwm functionality takes precedence. module base + 0x0018 76543210 r ptp7 ptp6 ptp5 ptp4 ptp3 ptp2 ptp1 ptp0 w pwm pwm7 pwm6 pwm5 pwm4 pwm3 pwm2 pwm1 pwm0 spi sck2 ss2 mosi2 miso2 ss1 sck1 mosi1 miso1 reset 0 0 0 00000 figure 4-23. port p i/o register (ptp) chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 159 4.3.4.2 port p input register (ptip) read: anytime. write: never, writes to this register have no effect. this register always reads back the status of the associated pins. 4.3.4.3 port p data direction register (ddrp) read: anytime. write: anytime. this register con?ures each port p pin as either input or output. if the associated pwm channel or spi module is enabled this register has no effect on the pins. the pwm forces the i/o state to be an output for each port line associated with an enabled pwm7-0 channel. channel 7 can force the pin to input if the shutdown feature is enabled. if a spi module is enabled, the spi determines the pin direction if the pwm, spi1 and spi2 functions are disabled, the corresponding data direction register bit reverts to control the i/o direction of the associated pin. module base + 0x0019 76543210 r ptip7 ptip6 ptip5 ptip4 ptip3 ptip2 ptip1 ptip0 w reset u u u uuuuu = reserved or unimplemented u = unaffected by reset figure 4-24. port p input register (ptip) module base + 0x001a 76543210 r ddrp7 ddrp6 ddrp5 ddrp4 ddrp3 ddrp2 ddrp1 ddrp0 w reset 0 0 0 00000 figure 4-25. port p data direction register (ddrp) table 4-24. ddrp field descriptions field description 7? ddrp[7:0] data direction port p 0 associated pin is con?ured as input. 1 associated pin is con?ured as output. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 160 freescale semiconductor 4.3.4.4 port p reduced drive register (rdrp) read: anytime. write: anytime. this register con?ures the drive strength of each port p output pin as either full or reduced. if the port is used as input this bit is ignored. 4.3.4.5 port p pull device enable register (perp) read: anytime. write: anytime. this register con?ures whether a pull-up or a pull-down device is activated, if the port is used as input. this bit has no effect if the port is used as output. out of reset no pull device is enabled. module base + 0x001b 76543210 r rdrp7 rdrp6 rdrp5 rdrp4 rdrp3 rdrp2 rdrp1 rdrp0 w reset 0 0 0 00000 figure 4-26. port p reduced drive register (rdrp) table 4-25. rdrp field descriptions field description 7? rdrp[7:0] reduced drive port p 0 full drive strength at output. 1 associated pin drives at about 1/6 of the full drive strength. module base + 0x001c 76543210 r perp7 perp6 perp5 perp4 perp3 perp2 perp1 perp0 w reset 0 0 0 00000 figure 4-27. port p pull device enable register (perp) table 4-26. perp field descriptions field description 7? perp[7:0] pull device enable port p 0 pull-up or pull-down device is disabled. 1 either a pull-up or pull-down device is enabled. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 161 4.3.4.6 port p polarity select register (ppsp) read: anytime. write: anytime. this register serves a dual purpose by selecting the polarity of the active interrupt edge as well as selecting a pull-up or pull-down device if enabled. 4.3.4.7 port p interrupt enable register (piep) read: anytime. write: anytime. this register disables or enables on a per pin basis the edge sensitive external interrupt associated with port p. module base + 0x001d 76543210 r ppsp7 ppsp6 ppsp5 ppsp4 ppsp3 ppsp2 ppsp1 ppsp0 w reset 0 0 0 00000 figure 4-28. port p polarity select register (ppsp) table 4-27. ppsp field descriptions field description 7? ppsp[7:0] polarity select port p 0 falling edge on the associated port p pin sets the associated ?g bit in the pifp register.a pull-up device is connected to the associated port p pin, if enabled by the associated bit in register perp and if the port is used as input. 1 rising edge on the associated port p pin sets the associated ?g bit in the pifp register.a pull-down device is connected to the associated port p pin, if enabled by the associated bit in register perp and if the port is used as input. module base + 0x001e 76543210 r piep7 piep6 piep5 piep4 piep3 piep2 piep1 piep0 w reset 0 0 0 00000 figure 4-29. port p interrupt enable register (piep) table 4-28. piep field descriptions field description 7? piep[7:0] interrupt enable port p 0 interrupt is disabled (interrupt ?g masked). 1 interrupt is enabled. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 162 freescale semiconductor 4.3.4.8 port p interrupt flag register (pifp) read: anytime. write: anytime. each ?g is set by an active edge on the associated input pin. this could be a rising or a falling edge based on the state of the ppsp register. to clear this ?g, write ? to the corresponding bit in the pifp register. writing a ??has no effect. module base + 0x001f 76543210 r pifp7 pifp6 pifp5 pifp4 pifp3 pifp2 pifp1 pifp0 w reset 0 0 0 00000 figure 4-30. port p interrupt flag register (pifp) table 4-29. field descriptions field description 7? pifp[7:0] interrupt flags port p 0 no active edge pending. writing a ??has no effect. 1 active edge on the associated bit has occurred (an interrupt will occur if the associated enable bit is set). writing a ??clears the associated ?g. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 163 4.3.5 port h registers port h is associated with two serial peripheral interfaces (spi1, spi2). each pin is assigned to these modules according to the following priority: spi2/sp1 > general-purpose i/o. when spi2 is enabled, the respective pin configuration for ph[7:4] is determined by several status bits in the spi2 module. when spi1 is enabled, the respective pin configuration for ph[3:0] is determined by several status bits in the spi1 module. refer to the spi block description chapter for information on enabling and disabling the spi. the spi1 and spi2 pins can be re-routed. refer to section 4.3.3.8, ?odule routing register (modrr) . during reset, port h pins are con?ured as high-impedance inputs. 4.3.5.1 port h i/o register (pth) read: anytime. write: anytime. if the data direction bits of the associated i/o pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. the spi function takes precedence over the general purpose i/o if enabled. . 4.3.5.2 port h input register (ptih) read: anytime. write: never, writes to this register have no effect. this register always reads back the status of the associated pins. module base + 0x0020 76543210 r pth7 pth6 pth5 pth4 pth3 pth2 pth1 pth0 w spi ss2 sck2 mosi2 miso2 ss1 sck1 mosi1 miso1 reset 0 0 0 00000 figure 4-31. port h i/o register (pth) module base + 0x0021 76543210 r ptih7 ptih6 ptih5 ptih4 ptih3 ptih2 ptih1 ptih0 w reset u u u uuuuu = reserved or unimplemented u = unaffected by reset figure 4-32. port h input register (ptih) chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 164 freescale semiconductor 4.3.5.3 port h data direction register (ddrh) read: anytime. write: anytime. this register con?ures each port h pin as either input or output. 4.3.5.4 port h reduced drive register (rdrh) read: anytime. write: anytime. this register con?ures the drive strength of each port h output pin as either full or reduced. if the port is used as input this bit is ignored. module base + 0x0022 76543210 r ddrh7 ddrh6 ddrh5 ddrh4 ddrh3 ddrh2 ddrh1 ddrh0 w reset 0 0 0 00000 figure 4-33. port h data direction register (ddrh) table 4-30. ddrh field descriptions field description 7? ddrh]7:0] data direction port h 0 associated pin is con?ured as input. 1 associated pin is con?ured as output. module base + 0x0023 76543210 r rdrh7 rdrh6 rdrh5 rdrh4 rdrh3 rdrh2 rdrh1 rdrh0 w reset 0 0 0 00000 figure 4-34. port h reduced drive register (rdrh) table 4-31. rdrh field descriptions field description 7? rdrh[7:0] reduced drive port h 0 full drive strength at output. 1 associated pin drives at about 1/6 of the full drive strength. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 165 4.3.5.5 port h pull device enable register (perh) read: anytime. write: anytime. this register con?ures whether a pull-up or a pull-down device is activated, if the port is used as input. this bit has no effect if the port is used as output. out of reset no pull device is enabled. 4.3.5.6 port h polarity select register (ppsh) read: anytime. write: anytime. this register serves a dual purpose by selecting the polarity of the active interrupt edge as well as selecting a pull-up or pull-down device if enabled. module base + 0x0024 76543210 r perh7 perh6 perh5 perh4 perh3 perh2 perh1 perh0 w reset 0 0 0 00000 figure 4-35. port h pull device enable register (perh) table 4-32. perh field descriptions field description 7? perh[7:0] pull device enable port h 0 pull-up or pull-down device is disabled. 1 either a pull-up or pull-down device is enabled. module base + 0x0025 76543210 r ppsh7 ppsh6 ppsh5 ppsh4 ppsh3 ppsh2 ppsh1 ppsh0 w reset 0 0 0 00000 figure 4-36. port h polarity select register (ppsh) table 4-33. ppsh field descriptions field description 7? ppsh[7:0] polarity select port h 0 falling edge on the associated port h pin sets the associated ?g bit in the pifh register. a pull-up device is connected to the associated port h pin, if enabled by the associated bit in register perh and if the port is used as input. 1 rising edge on the associated port h pin sets the associated ?g bit in the pifh register. a pull-down device is connected to the associated port h pin, if enabled by the associated bit in register perh and if the port is used as input. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 166 freescale semiconductor 4.3.5.7 port h interrupt enable register (pieh) read: anytime. write: anytime. this register disables or enables on a per pin basis the edge sensitive external interrupt associated with port h. 4.3.5.8 port h interrupt flag register (pifh) read: anytime. write: anytime. each ?g is set by an active edge on the associated input pin. this could be a rising or a falling edge based on the state of the ppsh register. to clear this ?g, write ? to the corresponding bit in the pifh register. writing a ??has no effect. module base + 0x0026 76543210 r pieh7 pieh6 pieh5 pieh4 pieh3 pieh2 pieh1 pieh0 w reset 0 0 0 00000 figure 4-37. port h interrupt enable register (pieh) table 4-34. pieh field descriptions field description 7? pieh[7:0] interrupt enable port h 0 interrupt is disabled (interrupt ?g masked). 1 interrupt is enabled. module base + 0x0027 76543210 r pifh7 pifh6 pifh5 pifh4 pifh3 pifh2 pifh1 pifh0 w reset 0 0 0 00000 figure 4-38. port h interrupt flag register (pifh) table 4-35. pifh field descriptions field description 7? pifh[7:0] interrupt flags port h 0 no active edge pending. writing a ??has no effect. 1 active edge on the associated bit has occurred (an interrupt will occur if the associated enable bit is set). writing a ??clears the associated ?g. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 167 4.3.6 port j registers port j is associated with freescale? scalable controller area network (can4) and inter-ic bus (iic) modules. each pin is assigned to these modules according to the following priority: can4 > iic > general-purpose i/o. the can4 function (txcan4 and rxcan4) takes precedence over the iic and the general purpose i/o function if the can4 module is enabled. refer to the mscan block description chapter for information on enabling and disabling can4 . the iic function (scl and sda) takes precedence over the general purpose i/o function if the iic is enabled. if the iic module takes precedence the sda and scl outputs are con?ured as open drain outputs. refer to the iic block description chapter for information on enabling and disabling the iic . during reset, port j pins are con?ured as inputs with pull-up. 4.3.6.1 port j i/o register (ptj) read: anytime. write: anytime. if the data direction bits of the associated i/o pins are set to 1, a read returns the value of the port register, otherwise the value at the pins is read. 4.3.6.2 port j input register (ptij) read: anytime. write: never, writes to this register have no effect. this register always reads back the status of the associated pins. module base + 0x0028 76543210 r ptj7 ptj6 0000 ptj1 ptj0 w can4 txcan4 rxcan4 iic scl sda reset 0 0 0 00000 = unimplemented or reserved figure 4-39. port j i/o register (ptj) module base + 0x0029 76543210 r ptij7 ptij6 0 0 0 0 ptij1 ptij0 w reset u u 0 000uu = reserved or unimplemented u = unaffected by reset figure 4-40. port j input register (ptij) chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 168 freescale semiconductor 4.3.6.3 port j data direction register (ddrj) read: anytime. write: anytime. this register con?ures each port j pin as either input or output. if enable, can4 forces the i/o state to be an output on pj7 (txcan4) and an input on pin pj6 (rxcan4). if can4 is disabled, the iic takes control of the i/o if enabled. in these cases the data direction bits will not change. the ddrj bits revert to controlling the i/o direction of a pin when the associated peripheral module is disabled. 4.3.6.4 port j reduced drive register (rdrj) read: anytime. write: anytime. this register con?ures the drive strength of each port j output pin as either full or reduced. if the port is used as input this bit is ignored. module base + 0x002a 76543210 r ddrj7 ddrj6 0000 ddrj1 ddrj0 w reset 0 0 0 0 = unimplemented or reserved figure 4-41. port j data direction register (ddrj) table 4-36. field descriptions field description 7, 6, 1, 0 ddrj[7:6] ddrj[1:0] data direction port j 0 associated pin is con?ured as input. 1 associated pin is con?ured as output. module base + 0x002b 76543210 r rdrj7 rdrj6 0000 rdrj1 rdrj0 w reset 0 0 0 0 = unimplemented or reserved figure 4-42. port j reduced drive register (rdrj) table 4-37. rdrj field descriptions field description 7, 6, 1, 0 rdrj[7:6] rdrj[1:0] reduced drive port j 0 full drive strength at output. 1 associated pin drives at about 1/6 of the full drive strength. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 169 4.3.6.5 port j pull device enable register (perj) read: anytime. write: anytime. this register con?ures whether a pull-up or a pull-down device is activated, if the port is used as input or as wired-or output. this bit has no effect if the port is used as push-pull output. out of reset a pull-up device is enabled. 4.3.6.6 port j polarity select register (ppsj) read: anytime. write: anytime. this register serves a dual purpose by selecting the polarity of the active interrupt edge as well as selecting a pull-up or pull-down device if enabled. module base + 0x002c 76543210 r perj7 perj6 0000 perj1 perj0 w reset 1 1 1 1 = unimplemented or reserved figure 4-43. port j pull device enable register (perj) table 4-38. perj field descriptions field description 7, 6, 1, 0 perj[7:6] perj[1:0] pull device enable port j 0 pull-up or pull-down device is disabled. 1 either a pull-up or pull-down device is enabled. module base + 0x002d 76543210 r ppsj7 ppsj6 0000 ppsj1 ppsj0 w reset 0 0 0 0 = unimplemented or reserved figure 4-44. port j polarity select register (ppsj) table 4-39. ppsj field descriptions field description 7, 6, 1, 0 ppsj[7:6] ppsj[1:0] polarity select port j 0 falling edge on the associated port j pin sets the associated ?g bit in the pifj register. a pull-up device is connected to the associated port j pin, if enabled by the associated bit in register perj and if the port is used as general purpose input or as iic port. 1 rising edge on the associated port j pin sets the associated ?g bit in the pifj register. a pull-down device is connected to the associated port j pin, if enabled by the associated bit in register perj and if the port is used as input. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 170 freescale semiconductor 4.3.6.7 port j interrupt enable register (piej) read: anytime. write: anytime. this register disables or enables on a per pin basis the edge sensitive external interrupt associated with port j. 4.3.6.8 port j interrupt flag register (pifj) read: anytime. write: anytime. each ?g is set by an active edge on the associated input pin. this could be a rising or a falling edge based on the state of the ppsj register. to clear this ?g, write ? to the corresponding bit in the pifj register. writing a ??has no effect. module base + 0x002e 76543210 r piej7 piej6 0000 piej1 piej0 w reset 0 0 0 0 = unimplemented or reserved figure 4-45. port j interrupt enable register (piej) table 4-40. piej field descriptions field description 7, 6, 1, 0 piej[7:6] piej[1:0] interrupt enable port j 0 interrupt is disabled (interrupt ?g masked). 1 interrupt is enabled. module base + 0x002f 76543210 r pifj7 pifj6 0000 pifj1 pifj0 w reset 0 0 0 0 = unimplemented or reserved figure 4-46. port j interrupt flag register (pifj) table 4-41. pifj field descriptions field description 7, 6, 1, 0 pifj[7:6] pifj[1:0] interrupt flags port j 0 no active edge pending. writing a ??has no effect. 1 active edge on the associated bit has occurred (an interrupt will occur if the associated enable bit is set). writing a ??clears the associated ?g. chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 171 4.4 functional description each pin can act as general purpose i/o. in addition the pin can act as an output from a peripheral module or an input to a peripheral module. table 4-42 summarizes the priority in case of multiple enabled modules trying to control a shared port. a set of con?uration registers is common to all ports. all registers can be written at any time, however a speci? con?uration might not become active. example: a selected pull-up resistor does not become active while the port is used as a push-pull output. 4.4.1 i/o register the i/o register holds the value driven out to the pin if the port is used as a general-purpose i/o. writing to the i/o register only has an effect on the pin if the port is used as general-purpose output. when reading the i/o register, the value of each pin is returned if the corresponding data direction register bit is set to 0 (pin configured as input). if the data direction register bits is set to 1, the content of the i/o register bit is returned. this is independent of any other configuration ( figure 4-47 ). due to internal synchronization circuits, it can take up to 2 bus cycles until the correct value is read on the i/o register when changing the data direction register. 4.4.2 input register the input register is a read-only register and generally returns the value of the pin ( figure 4-47 ). it can be used to detect overload or short circuit conditions. due to internal synchronization circuits, it can take up to 2 bus cycles until the correct value is read on the input register when changing the data direction register. table 4-42. summary of functional priority port priority 1 1 highest priority >... > lowest priority t timer > gpio s sci0, sci1, spi0 > gpio m can0 > gpio can0 (routed) > spi0 (routed) > gpio can0 (routed) > can4 (routed) > spi0 (routed) > gpio can4 (routed) > gpio p pwm > spi1, spi2 > gpio h spi1, spi2 > gpio j can4 > iic > gpio chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 172 freescale semiconductor 4.4.3 data direction register the data direction register defines whether the pin is used as an input or an output. a data direction register bit set to 0 configures the pin as an input. a data direction register bit set to 0 configures the pin as an output. if a peripheral module controls the pin the contents of the data direction register is ignored ( figure 4-47 ). figure 4-47. illustration of i/o pin functionality figure 4-48 shows the state of digital inputs and outputs when an analog module drives the port. when the analog module is enabled all associated digital output ports are disabled and all associated digital input ports read ?? figure 4-48. digital ports and analog module 4.4.4 reduced drive register if the port is used as an output the reduced drive register allows the configuration of the drive strength. ptx ddrx output enable module enable 1 0 1 1 0 0 pad ptix data out digital module analog module 1 0 1 pad digital input digital output 1 0 analog module enable output pim boundary chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 173 4.4.5 pull device enable register the pull device enable register turns on a pull-up or pull-down device. the pull device becomes active only if the pin is used as an input or as a wired-or output. 4.4.6 polarity select register the polarity select register selects either a pull-up or pull-down device if enabled. the pull device becomes active only if the pin is used as an input or as a wired-or output. 4.4.7 pin con?uration summary the following table summarizes the effect on the various con?uration bits, data direction (ddr), output level (i/o), reduced drive (rdr), pull enable (pe), pull select (ps) and interrupt enable (ie) for the ports. the con?uration bit ps is used for two purposes: 1. con?ure the sensitive interrupt edge (rising or falling), if interrupt is enabled. 2. select either a pull-up or pull-down device if pe is active. note all bits of all registers in this module are completely synchronous to internal clocks during a register read. table 4-43. pin con?uration summary ddr io rdr pe ps ie 1 1 applicable only on port p, h, and j. function pull device interrupt 0 x x 0 x 0 input disabled disabled 0 x x 1 0 0 input pull up disabled 0 x x 1 1 0 input pull down disabled 0 x x 0 0 1 input disabled falling edge 0 x x 0 1 1 input disabled rising edge 0 x x 1 0 1 input pull up falling edge 0 x x 1 1 1 input pull down rising edge 1 0 0 x x 0 output, full drive to 0 disabled disabled 1 1 0 x x 0 output, full drive to 1 disabled disabled 1 0 1 x x 0 output, reduced drive to 0 disabled disabled 1 1 1 x x 0 output, reduced drive to 1 disabled disabled 1 0 0 x 0 1 output, full drive to 0 disabled falling edge 1 1 0 x 1 1 output, full drive to 1 disabled rising edge 1 0 1 x 0 1 output, reduced drive to 0 disabled falling edge 1 1 1 x 1 1 output, reduced drive to 1 disabled rising edge chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 174 freescale semiconductor 4.5 resets the reset values of all registers are given in the register description in section 4.3, ?emory map and register de?ition . 4.5.1 reset initialization all registers including the data registers get set/reset asynchronously. table 4-44 summarizes the port properties after reset initialization. 4.6 interrupts 4.6.1 general port p, h and j generate a separate edge sensitive interrupt if enabled. each port offers i/o pins with edge triggered interrupt capability in wired-or fashion. the interrupt enable as well as the sensitivity to rising or falling edges can be individually configured on per pin basis. all bits/pins per port share the same interrupt vector. interrupts can be used with the pins configured as inputs or outputs. an interrupt is generated when a bit in the port interrupt flag register and its corresponding port interrupt enable bit are both set. this external interrupt feature is capable to wake up the cpu when it is in stop or wait mode. a digital filter on each pin prevents pulses ( figure 4-49 ) shorter than a specified time from generating an interrupt. the minimum time varies over process conditions, temperature and voltage ( figure 4-50 and table 4-45 ). figure 4-49. pulse illustration table 4-44. port reset state summary port reset states data direction pull mode reduced drive wired-or mode interrupt t input hi-z disabled n/a n/a s input pull-up disabled disabled n/a m input hi-z disabled disabled n/a p input hi-z disabled n/a disabled h input hi-z disabled n/a disabled j input pull-up disabled n/a disabled t pulse chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 175 figure 4-50. interrupt glitch filter (pps = 0) a valid edge on an input is detected if 4 consecutive samples of a passive level are followed by 4 consecutive samples of an active level directly or indirectly. the filters are continuously clocked by the bus clock in run and wait mode. in stop mode the clock is generated by a single rc oscillator in the port integration module. to maximize current saving the rc oscillator runs only if the following condition is true on any pin: sample count <= 4 and port interrupt enabled (pie=1) and port interrupt flag not set (pif=0). table 4-45. pulse detection criteria pulse mode st op stop 1 1 these values include the spread of the oscillator frequency over temperature, voltage and process. unit unit ignored t pulse <= 3 bus clock t pulse <= 3.2 s uncertain 3 < t pulse < 4 bus clock 3.2 < t pulse < 10 s valid t pulse >= 4 bus clock t pulse >= 10 s glitch, ?tered out, no interrupt ?g set valid pulse, interrupt ?g set t ifmin t ifmax chapter 4 port integration module (pim9kg128v1) mc9s12kg128 data sheet, rev. 1.15 176 freescale semiconductor 4.6.2 interrupt sources note vector addresses and their relative interrupt priority are determined at the mcu level. 4.6.3 operation in stop mode all clocks are stopped in stop mode. the port integration module has asynchronous paths on port p, h and j to generate wake-up interrupts from stop mode. for other sources of external interrupts refer to the respective block description chapters. table 4-46. port integration module interrupt sources interrupt source interrupt flag local enable global (ccr) mask port p pifp[7:0] piep[7:0] i bit port h pifh[7:0] pieh[7:0] i bit port j pifj[7:6,1:0] piej[7:6,1:0] i bit mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 177 chapter 5 clocks and reset generator (crgv4) 5.1 introduction this speci?ation describes the function of the clocks and reset generator (crg). 5.1.1 features the main features of this block are: phase-locked loop (pll) frequency multiplier reference divider automatic bandwidth control mode for low-jitter operation automatic frequency lock detector cpu interrupt on entry or exit from locked condition self-clock mode in absence of reference clock system clock generator clock quality check clock switch for either oscillator- or pll-based system clocks user selectable disabling of clocks during wait mode for reduced power consumption computer operating properly (cop) watchdog timer with time-out clear window system reset generation from the following possible sources: power-on reset low voltage reset refer to the device overview section for availability of this feature. cop reset loss of clock reset external pin reset real-time interrupt (rti) chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 178 freescale semiconductor 5.1.2 modes of operation this subsection lists and brie? describes all operating modes supported by the crg. run mode all functional parts of the crg are running during normal run mode. if rti or cop functionality is required the individual bits of the associated rate select registers (copctl, rtictl) have to be set to a nonzero value. wait mode this mode allows to disable the system and core clocks depending on the con?uration of the individual bits in the clksel register. stop mode depending on the setting of the pstp bit, stop mode can be differentiated between full stop mode (pstp = 0) and pseudo-stop mode (pstp = 1). full stop mode the oscillator is disabled and thus all system and core clocks are stopped. the cop and the rti remain frozen. pseudo-stop mode the oscillator continues to run and most of the system and core clocks are stopped. if the respective enable bits are set the cop and rti will continue to run, else they remain frozen. self-clock mode self-clock mode will be entered if the clock monitor enable bit (cme) and the self-clock mode enable bit (scme) are both asserted and the clock monitor in the oscillator block detects a loss of clock. as soon as self-clock mode is entered the crg starts to perform a clock quality check. self-clock mode remains active until the clock quality check indicates that the required quality of the incoming clock signal is met (frequency and amplitude). self-clock mode should be used for safety purposes only. it provides reduced functionality to the mcu in case a loss of clock is causing severe system conditions. 5.1.3 block diagram figure 5-1 shows a block diagram of the crg. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 179 figure 5-1. crg block diagram 5.2 external signal description this section lists and describes the signals that connect off chip. 5.2.1 v ddpll , v sspll ?pll operating voltage, pll ground these pins provides operating voltage (v ddpll ) and ground (v sspll ) for the pll circuitry. this allows the supply voltage to the pll to be independently bypassed. even if pll usage is not required v ddpll and v sspll must be connected properly. 5.2.2 xfc ?pll loop filter pin a passive external loop ?ter must be placed on the xfc pin. the ?ter is a second-order, low-pass ?ter to eliminate the vco input ripple. the value of the external ?ter network and the reference frequency determines the speed of the corrections and the stability of the pll. refer to the device overview chapter for calculation of pll loop ?ter (xfc) components. if pll usage is not required the xfc pin must be tied to v ddpll . crg registers clock and reset cop reset rti pll xfc v ddpll v sspll oscil- extal xtal control bus clock system reset oscillator clock pllclk oscclk core clock clock monitor cm fail clock quality checker reset generator xclks power-on reset low voltage reset 1 cop timeout real-time interrupt pll lock interrupt self-clock mode interrupt lator voltage regulator 1 refer to the device overview section for availability of the low-voltage reset feature. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 180 freescale semiconductor figure 5-2. pll loop filter connections 5.2.3 reset ?reset pin reset is an active low bidirectional reset pin. as an input it initializes the mcu asynchronously to a known start-up state. as an open-drain output it indicates that an system reset (internal to mcu) has been triggered. 5.3 memory map and register de?ition this section provides a detailed description of all registers accessible in the crg. 5.3.1 module memory map table 5-1 gives an overview on all crg registers. table 5-1. crg memory map address offset use access 0x0000 crg synthesizer register (synr) r/w 0x0001 crg reference divider register (refdv) r/w 0x0002 crg test flags register (ctflg) 1 1 ctflg is intended for factory test purposes only. r/w 0x0003 crg flags register (crgflg) r/w 0x0004 crg interrupt enable register (crgint) r/w 0x0005 crg clock select register (clksel) r/w 0x0006 crg pll control register (pllctl) r/w 0x0007 crg rti control register (rtictl) r/w 0x0008 crg cop control register (copctl) r/w 0x0009 crg force and bypass test register (forbyp) 2 2 forbyp is intended for factory test purposes only. r/w 0x000a crg test control register (ctctl) 3 3 ctctl is intended for factory test purposes only. r/w 0x000b crg cop arm/timer reset (armcop) r/w mcu xfc rs cs v ddpll cp chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 181 note register address = base address + address offset, where the base address is de?ed at the mcu level and the address offset is de?ed at the module level. 5.3.2 register descriptions this section describes in address order all the crg registers and their individual bits. register name bit 7 654321 bit 0 synr r 0 0 syn5 syn4 syn3 syn2 syn1 syn0 w refdv r 0000 refdv3 refdv2 refdv1 refdv0 w ctflg r 00000000 w crgflg r rtif porf lvrf lockif lock track scmif scm w crgint r rtie 00 lockie 00 scmie 0 w clksel r pllsel pstp syswai roawai pllwai cwai rtiwai copwai w pllctl r cme pllon auto acq 0 pre pce scme w rtictl r 0 rtr6 rtr5 rtr4 rtr3 rtr2 rtr1 rtr0 w copctl r wcop rsbck 000 cr2 cr1 cr0 w forbyp r 00000000 w ctctl r 00000000 w = unimplemented or reserved figure 5-3. crg register summary chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 182 freescale semiconductor 5.3.2.1 crg synthesizer register (synr) the synr register controls the multiplication factor of the pll. if the pll is on, the count in the loop divider (synr) register effectively multiplies up the pll clock (pllclk) from the reference frequency by 2 x (synr+1). pllclk will not be below the minimum vco frequency (f scm ). note if pll is selected (pllsel=1), bus clock = pllclk / 2 bus clock must not exceed the maximum operating system frequency. read: anytime write: anytime except if pllsel = 1 note write to this register initializes the lock detector bit and the track detector bit. armcop r 00000000 w bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 76543210 r0 0 syn5 synr syn3 syn2 syn1 syn0 w reset 0 0 0 00000 = unimplemented or reserved figure 5-4. crg synthesizer register (synr) register name bit 7 654321 bit 0 = unimplemented or reserved figure 5-3. crg register summary (continued) pllclk 2xoscclkx synr 1 + () refdv 1 + () ---------------------------------- - = chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 183 5.3.2.2 crg reference divider register (refdv) the refdv register provides a ?er granularity for the pll multiplier steps. the count in the reference divider divides oscclk frequency by refdv + 1. read: anytime write: anytime except when pllsel = 1 note write to this register initializes the lock detector bit and the track detector bit. 5.3.2.3 reserved register (ctflg) this register is reserved for factory testing of the crg module and is not available in normal modes. read: always reads 0x0000 in normal modes write: unimplemented in normal modes note writing to this register when in special mode can alter the crg functionality. 76543210 r0000 refdv3 refdv2 refdv1 refdv0 w reset 0 0 0 00000 = unimplemented or reserved figure 5-5. crg reference divider register (refdv) 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 5-6. crg reserved register (ctflg) chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 184 freescale semiconductor 5.3.2.4 crg flags register (crgflg) this register provides crg status bits and ?gs. read: anytime write: refer to each bit for individual write conditions 76543210 r rtif porf lvrf lockif lock track scmif scm w reset 0 note 1 note 2 00000 1. porf is set to 1 when a power-on reset occurs. unaffected by system reset. 2. lvrf is set to 1 when a low-voltage reset occurs. unaffected by system reset. = unimplemented or reserved figure 5-7. crg flag register (crgflg) table 5-2. crgflg field descriptions field description 7 rtif real-time interrupt flag rtif is set to 1 at the end of the rti period. this ?g can only be cleared by writing a 1. writing a 0 has no effect. if enabled (rtie = 1), rtif causes an interrupt request. 0 rti time-out has not yet occurred. 1 rti time-out has occurred. 6 porf power-on reset flag porf is set to 1 when a power-on reset occurs. this ?g can only be cleared by writing a 1. writing a 0 has no effect. 0 power-on reset has not occurred. 1 power-on reset has occurred. 5 lvrf low-voltage reset flag if low voltage reset feature is not available (see the device overview chapter), lvrf always reads 0. lvrf is set to 1 when a low voltage reset occurs. this ?g can only be cleared by writing a 1. writing a 0 has no effect. 0 low voltage reset has not occurred. 1 low voltage reset has occurred. 4 lockif pll lock interrupt flag lockif is set to 1 when lock status bit changes. this ?g can only be cleared by writing a 1. writing a 0 has no effect.if enabled (lockie = 1), lockif causes an interrupt request. 0 no change in lock bit. 1 lock bit has changed. 3 lock lock status bit lock re?cts the current state of pll lock condition. this bit is cleared in self-clock mode. writes have no effect. 0 pll vco is not within the desired tolerance of the target frequency. 1 pll vco is within the desired tolerance of the target frequency. 2 track track status bit track re?cts the current state of pll track condition. this bit is cleared in self-clock mode. writes have no effect. 0 acquisition mode status. 1 tracking mode status. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 185 5.3.2.5 crg interrupt enable register (crgint) this register enables crg interrupt requests. read: anytime write: anytime 1 scmif self-clock mode interrupt flag ?scmif is set to 1 when scm status bit changes. this ?g can only be cleared by writing a 1. writing a 0 has no effect. if enabled (scmie=1), scmif causes an interrupt request. 0 no change in scm bit. 1 scm bit has changed. 0 scm self-clock mode status bit ?scm re?cts the current clocking mode. writes have no effect. 0 mcu is operating normally with oscclk available. 1 mcu is operating in self-clock mode with oscclk in an unknown state. all clocks are derived from pllclk running at its minimum frequency f scm . 76543210 r rtie 00 lockie 00 scmie 0 w reset 0 0 0 00000 = unimplemented or reserved figure 5-8. crg interrupt enable register (crgint) table 5-3. crgint field descriptions field description 7 rtie real-time interrupt enable bit 0 interrupt requests from rti are disabled. 1 interrupt will be requested whenever rtif is set. 4 lockie lock interrupt enable bit 0 lock interrupt requests are disabled. 1 interrupt will be requested whenever lockif is set. 1 scmie self-clock mode interrupt enable bit 0 scm interrupt requests are disabled. 1 interrupt will be requested whenever scmif is set. table 5-2. crgflg field descriptions (continued) field description chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 186 freescale semiconductor 5.3.2.6 crg clock select register (clksel) this register controls crg clock selection. refer to figure 5-17 for details on the effect of each bit. read: anytime write: refer to each bit for individual write conditions 76543210 r pllsel pstp syswai roawai pllwai cwai rtiwai copwai w reset 0 0 0 00000 figure 5-9. crg clock select register (clksel) table 5-4. clksel field descriptions field description 7 pllsel pll select bit write anytime. writing a 1 when lock = 0 and auto = 1, or track = 0 and auto = 0 has no effect. this prevents the selection of an unstable pllclk as sysclk. pllsel bit is cleared when the mcu enters self-clock mode, stop mode or wait mode with pllwai bit set. 0 system clocks are derived from oscclk (bus clock = oscclk / 2). 1 system clocks are derived from pllclk (bus clock = pllclk / 2). 6 pstp pseudo-stop bit ?write: anytime ?this bit controls the functionality of the oscillator during stop mode. 0 oscillator is disabled in stop mode. 1 oscillator continues to run in stop mode (pseudo-stop). the oscillator amplitude is reduced. refer to oscillator block description for availability of a reduced oscillator amplitude. note: pseudo-stop allows for faster stop recovery and reduces the mechanical stress and aging of the resonator in case of frequent stop conditions at the expense of a slightly increased power consumption. note: lower oscillator amplitude exhibits lower power consumption but could have adverse effects during any electro-magnetic susceptibility (ems) tests. 5 syswai system clocks stop in wait mode bit ?write: anytime 0 in wait mode, the system clocks continue to run. 1 in wait mode, the system clocks stop. note: rti and cop are not affected by syswai bit. 4 roawai reduced oscillator amplitude in wait mode bit ?write: anytime ?refer to oscillator block description chapter for availability of a reduced oscillator amplitude. if no such feature exists in the oscillator block then setting this bit to 1 will not have any effect on power consumption. 0 normal oscillator amplitude in wait mode. 1 reduced oscillator amplitude in wait mode. note: lower oscillator amplitude exhibits lower power consumption but could have adverse effects during any electro-magnetic susceptibility (ems) tests. 3 pllwai pll stops in wait mode bit ?write: anytime ?if pllwai is set, the crg will clear the pllsel bit before entering wait mode. the pllon bit remains set during wait mode but the pll is powered down. upon exiting wait mode, the pllsel bit has to be set manually if pll clock is required. while the pllwai bit is set the auto bit is set to 1 in order to allow the pll to automatically lock on the selected target frequency after exiting wait mode. 0 pll keeps running in wait mode. 1 pll stops in wait mode. 2 cwai core stops in wait mode bit ?write: anytime 0 core clock keeps running in wait mode. 1 core clock stops in wait mode. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 187 5.3.2.7 crg pll control register (pllctl) this register controls the pll functionality. read: anytime write: refer to each bit for individual write conditions 1 rtiwai rti stops in wait mode bit ?write: anytime 0 rti keeps running in wait mode. 1 rti stops and initializes the rti dividers whenever the part goes into wait mode. 0 copwai cop stops in wait mode bit ?normal modes: write once ?pecial modes: write anytime 0 cop keeps running in wait mode. 1 cop stops and initializes the cop dividers whenever the part goes into wait mode. 76543210 r cme pllon auto acq 0 pre pce scme w reset 1 1 1 10001 = unimplemented or reserved figure 5-10. crg pll control register (pllctl) table 5-5. pllctl field descriptions field description 7 cme clock monitor enable bit ?cme enables the clock monitor. write anytime except when scm = 1. 0 clock monitor is disabled. 1 clock monitor is enabled. slow or stopped clocks will cause a clock monitor reset sequence or self-clock mode. note: operating with cme = 0 will not detect any loss of clock. in case of poor clock quality this could cause unpredictable operation of the mcu. note: in stop mode (pstp = 0) the clock monitor is disabled independently of the cme bit setting and any loss of clock will not be detected. 6 pllon phase lock loop on bit pllon turns on the pll circuitry. in self-clock mode, the pll is turned on, but the pllon bit reads the last latched value. write anytime except when pllsel = 1. 0 pll is turned off. 1 pll is turned on. if auto bit is set, the pll will lock automatically. 5 auto automatic bandwidth control bit ?auto selects either the high bandwidth (acquisition) mode or the low bandwidth (tracking) mode depending on how close to the desired frequency the vco is running. write anytime except when pllwai=1, because pllwai sets the auto bit to 1. 0 automatic mode control is disabled and the pll is under software control, using acq bit. 1 automatic mode control is enabled and acq bit has no effect. 4 acq acquisition bit ?write anytime. if auto=1 this bit has no effect. 0 low bandwidth ?ter is selected. 1 high bandwidth ?ter is selected. table 5-4. clksel field descriptions (continued) field description chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 188 freescale semiconductor 5.3.2.8 crg rti control register (rtictl) this register selects the timeout period for the real-time interrupt. read: anytime write: anytime note a write to this register initializes the rti counter. 2 pre rti enable during pseudo-stop bit ?pre enables the rti during pseudo-stop mode. write anytime. 0 rti stops running during pseudo-stop mode. 1 rti continues running during pseudo-stop mode. note: if the pre bit is cleared the rti dividers will go static while pseudo-stop mode is active. the rti dividers will not initialize like in wait mode with rtiwai bit set. 1 pce cop enable during pseudo-stop bit ?pce enables the cop during pseudo-stop mode. write anytime. 0 cop stops running during pseudo-stop mode 1 cop continues running during pseudo-stop mode note: if the pce bit is cleared the cop dividers will go static while pseudo-stop mode is active. the cop dividers will not initialize like in wait mode with copwai bit set. 0 scme self-clock mode enable bit normal modes: write once ?pecial modes: write anytime scme can not be cleared while operating in self-clock mode (scm=1). 0 detection of crystal clock failure causes clock monitor reset (see section 5.5.1, ?lock monitor reset ?. 1 detection of crystal clock failure forces the mcu in self-clock mode (see section 5.4.7.2, ?elf-clock mode ?. 76543210 r0 rtr6 rtr5 rtr4 rtr3 rtr2 rtr1 rtr0 w reset 0 0 0 00000 = unimplemented or reserved figure 5-11. crg rti control register (rtictl) table 5-6. rtictl field descriptions field description 6:4 rtr[6:4] real-time interrupt prescale rate select bits these bits select the prescale rate for the rti. see table 5-7 . 3:0 rtr[3:0] real-time interrupt modulus counter select bits ?these bits select the modulus counter target value to provide additional granularity. table 5-7 shows all possible divide values selectable by the rtictl register. the source clock for the rti is oscclk. table 5-5. pllctl field descriptions (continued) field description chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 189 table 5-7. rti frequency divide rates rtr[3:0] rtr[6:4] = 000 (off) 001 (2 10 ) 010 (2 11 ) 011 (2 12 ) 100 (2 13 ) 101 (2 14 ) 110 (2 15 ) 111 (2 16 ) 0000 ( 1) off * 2 10 2 11 2 12 2 13 2 14 2 15 2 16 0001 ( 2) off * 2x2 10 2x2 11 2x2 12 2x2 13 2x2 14 2x2 15 2x2 16 0010 ( 3) off * 3x2 10 3x2 11 3x2 12 3x2 13 3x2 14 3x2 15 3x2 16 0011 ( 4) off * 4x2 10 4x2 11 4x2 12 4x2 13 4x2 14 4x2 15 4x2 16 0100 ( 5) off * 5x2 10 5x2 11 5x2 12 5x2 13 5x2 14 5x2 15 5x2 16 0101 ( 6) off * 6x2 10 6x2 11 6x2 12 6x2 13 6x2 14 6x2 15 6x2 16 0110 ( 7) off * 7x2 10 7x2 11 7x2 12 7x2 13 7x2 14 7x2 15 7x2 16 0111 ( 8) off * 8x2 10 8x2 11 8x2 12 8x2 13 8x2 14 8x2 15 8x2 16 1000 ( 9) off * 9x2 10 9x2 11 9x2 12 9x2 13 9x2 14 9x2 15 9x2 16 1001 ( 10) off * 10x2 10 10x2 11 10x2 12 10x2 13 10x2 14 10x2 15 10x2 16 1010 ( 11) off * 11x2 10 11x2 11 11x2 12 11x2 13 11x2 14 11x2 15 11x2 16 1011 ( 12) off * 12x2 10 12x2 11 12x2 12 12x2 13 12x2 14 12x2 15 12x2 16 1100 ( 13) off * 13x2 10 13x2 11 13x2 12 13x2 13 13x2 14 13x2 15 13x2 16 1101 ( 14) off * 14x2 10 14x2 11 14x2 12 14x2 13 14x2 14 14x2 15 14x2 16 1110 ( 15) off * 15x2 10 15x2 11 15x2 12 15x2 13 15x2 14 15x2 15 15x2 16 1111 ( 16) off * 16x2 10 16x2 11 16x2 12 16x2 13 16x2 14 16x2 15 16x2 16 * denotes the default value out of reset.this value should be used to disable the rti to ensure future backwards compatibility. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 190 freescale semiconductor 5.3.2.9 crg cop control register (copctl) this register controls the cop (computer operating properly) watchdog. read: anytime write: wcop, cr2, cr1, cr0: once in user mode, anytime in special mode write: rsbck: once 76543210 r wcop rsbck 000 cr2 cr1 cr0 w reset 0 0 0 00000 = unimplemented or reserved figure 5-12. crg cop control register (copctl) table 5-8. copctl field descriptions field description 7 wcop window cop mode bit when set, a write to the armcop register must occur in the last 25% of the selected period. a write during the ?st 75% of the selected period will reset the part. as long as all writes occur during this window, 0x0055 can be written as often as desired. as soon as 0x00aa is written after the 0x0055, the time-out logic restarts and the user must wait until the next window before writing to armcop. table 5-9 shows the exact duration of this window for the seven available cop rates. 0 normal cop operation 1 window cop operation 6 rsbck cop and rti stop in active bdm mode bit 0 allows the cop and rti to keep running in active bdm mode. 1 stops the cop and rti counters whenever the part is in active bdm mode. 2:0 cr[2:0] cop watchdog timer rate select ?these bits select the cop time-out rate (see table 5-9 ). the cop time-out period is oscclk period divided by cr[2:0] value. writing a nonzero value to cr[2:0] enables the cop counter and starts the time-out period. a cop counter time-out causes a system reset. this can be avoided by periodically (before time-out) reinitializing the cop counter via the armcop register . table 5-9. cop watchdog rates 1 1 oscclk cycles are referenced from the previous cop time-out reset (writing 0x0055/0x00aa to the armcop register) cr2 cr1 cr0 oscclk cycles to time out 0 0 0 cop disabled 001 2 14 010 2 16 011 2 18 100 2 20 101 2 22 110 2 23 111 2 24 chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 191 5.3.2.10 reserved register (forbyp) note this reserved register is designed for factory test purposes only, and is not intended for general user access. writing to this register when in special modes can alter the crg s functionality. read: always read 0x0000 except in special modes write: only in special modes 5.3.2.11 reserved register (ctctl) note this reserved register is designed for factory test purposes only, and is not intended for general user access. writing to this register when in special test modes can alter the crg s functionality. read: always read 0x0080 except in special modes write: only in special modes 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 5-13. reserved register (forbyp) 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 5-14. reserved register (ctctl) chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 192 freescale semiconductor 5.3.2.12 crg cop timer arm/reset register (armcop) this register is used to restart the cop time-out period. read: always reads 0x0000 write: anytime when the cop is disabled (cr[2:0] = ?00? writing to this register has no effect. when the cop is enabled by setting cr[2:0] nonzero, the following applies: writing any value other than 0x0055 or 0x00aa causes a cop reset. to restart the cop time-out period you must write 0x0055 followed by a write of 0x00aa. other instructions may be executed between these writes but the sequence (0x0055, 0x00aa) must be completed prior to cop end of time-out period to avoid a cop reset. sequences of 0x0055 writes or sequences of 0x00aa writes are allowed. when the wcop bit is set, 0x0055 and 0x00aa writes must be done in the last 25% of the selected time-out period; writing any value in the ?st 75% of the selected period will cause a cop reset. 5.4 functional description this section gives detailed informations on the internal operation of the design. 5.4.1 phase locked loop (pll) the pll is used to run the mcu from a different time base than the incoming oscclk. for increased ?xibility, oscclk can be divided in a range of 1 to 16 to generate the reference frequency. this offers a ?er multiplication granularity. the pll can multiply this reference clock by a multiple of 2, 4, 6,... 126,128 based on the synr register. caution although it is possible to set the two dividers to command a very high clock frequency, do not exceed the speci?d bus frequency limit for the mcu. if (pllsel = 1), bus clock = pllclk / 2 the pll is a frequency generator that operates in either acquisition mode or tracking mode, depending on the difference between the output frequency and the target frequency. the pll can change between acquisition and tracking modes either automatically or manually. 76543210 r00000000 w bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 reset 0 0 0 00000 figure 5-15. armcop register diagram pllclk 2 oscclk synr 1 + [] refdv 1 + [] ---------------------------------- - = chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 193 the vco has a minimum operating frequency, which corresponds to the self-clock mode frequency f scm . figure 5-16. pll functional diagram 5.4.1.1 pll operation the oscillator output clock signal (oscclk) is fed through the reference programmable divider and is divided in a range of 1 to 16 (refdv+1) to output the reference clock. the vco output clock, (pllclk) is fed back through the programmable loop divider and is divided in a range of 2 to 128 in increments of [2 x (synr +1)] to output the feedback clock. see figure 5-16 . the phase detector then compares the feedback clock, with the reference clock. correction pulses are generated based on the phase difference between the two signals. the loop ?ter then slightly alters the dc voltage on the external ?ter capacitor connected to xfc pin, based on the width and direction of the correction pulse. the ?ter can make fast or slow corrections depending on its mode, as described in the next subsection. the values of the external ?ter network and the reference frequency determine the speed of the corrections and the stability of the pll. 5.4.1.2 acquisition and tracking modes the lock detector compares the frequencies of the feedback clock, and the reference clock. therefore, the speed of the lock detector is directly proportional to the ?al reference frequency. the circuit determines the mode of the pll and the lock condition based on this comparison. reduced consumption oscillator extal xtal oscclk pllclk reference programmable divider pdet phase detector refdv <3:0> loop programmable divider syn <5:0> cpump vco lock loop filter xfc pin up down lock detector reference feedback vddpll vddpll/vsspll crystal monitor vddpll/vsspll vdd/vss supplied by: chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 194 freescale semiconductor the pll ?ter can be manually or automatically con?ured into one of two possible operating modes: acquisition mode in acquisition mode, the ?ter can make large frequency corrections to the vco. this mode is used at pll start-up or when the pll has suffered a severe noise hit and the vco frequency is far off the desired frequency. when in acquisition mode, the track status bit is cleared in the crgflg register. tracking mode in tracking mode, the ?ter makes only small corrections to the frequency of the vco. pll jitter is much lower in tracking mode, but the response to noise is also slower. the pll enters tracking mode when the vco frequency is nearly correct and the track bit is set in the crgflg register. the pll can change the bandwidth or operational mode of the loop ?ter manually or automatically. in automatic bandwidth control mode (auto = 1), the lock detector automatically switches between acquisition and tracking modes. automatic bandwidth control mode also is used to determine when the pll clock (pllclk) is safe to use as the source for the system and core clocks. if pll lock interrupt requests are enabled, the software can wait for an interrupt request and then check the lock bit. if cpu interrupts are disabled, software can poll the lock bit continuously (during pll start-up, usually) or at periodic intervals. in either case, only when the lock bit is set, is the pllclk clock safe to use as the source for the system and core clocks. if the pll is selected as the source for the system and core clocks and the lock bit is clear, the pll has suffered a severe noise hit and the software must take appropriate action, depending on the application. the following conditions apply when the pll is in automatic bandwidth control mode (auto = 1): the track bit is a read-only indicator of the mode of the ?ter. the track bit is set when the vco frequency is within a certain tolerance, ? trk , and is clear when the vco frequency is out of a certain tolerance, ? unt . the lock bit is a read-only indicator of the locked state of the pll. the lock bit is set when the vco frequency is within a certain tolerance, ? lock , and is cleared when the vco frequency is out of a certain tolerance, ? unl . cpu interrupts can occur if enabled (lockie = 1) when the lock condition changes, toggling the lock bit. the pll can also operate in manual mode (auto = 0). manual mode is used by systems that do not require an indicator of the lock condition for proper operation. such systems typically operate well below the maximum system frequency (f sys ) and require fast start-up. the following conditions apply when in manual mode: acq is a writable control bit that controls the mode of the ?ter. before turning on the pll in manual mode, the acq bit should be asserted to con?ure the ?ter in acquisition mode. after turning on the pll by setting the pllon bit software must wait a given time (t acq ) before entering tracking mode (acq = 0). after entering tracking mode software must wait a given time (t al ) before selecting the pllclk as the source for system and core clocks (pllsel = 1). chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 195 5.4.2 system clocks generator figure 5-17. system clocks generator the clock generator creates the clocks used in the mcu (see figure 5-17 ). the gating condition placed on top of the individual clock gates indicates the dependencies of different modes (stop, wait) and the setting of the respective con?uration bits. the peripheral modules use the bus clock. some peripheral modules also use the oscillator clock. the memory blocks use the bus clock. if the mcu enters self-clock mode (see section 5.4.7.2, ?elf-clock mode ?, oscillator clock source is switched to pllclk running at its minimum frequency f scm . the bus clock is used to generate the clock visible at the eclk pin. the core clock signal is the clock for the cpu. the core clock is twice the bus clock as shown in figure 5-18 . but note that a cpu cycle corresponds to one bus clock. pll clock mode is selected with pllsel bit in the clksel register. when selected, the pll output clock drives sysclk for the main system including the cpu and peripherals. the pll cannot be turned off by clearing the pllon bit, if the pll clock is selected. when pllsel is changed, it takes a maximum oscillator phase lock loop extal xtal sysclk rti oscclk pllclk clock phase generator bus clock clock monitor 1 0 pllsel or scm 2 core clock cop oscillator oscillator = clock gate gating condition wait(cwai,syswai), stop wait(rtiwai), stop( pstp, pre), rti enable wait(copwai), stop( pstp, pce), cop enable wait(syswai), stop stop( pstp) 1 0 scm wait(syswai), stop clock clock (running during pseudo-stop mode chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 196 freescale semiconductor of 4 oscclk plus 4 pllclk cycles to make the transition. during the transition, all clocks freeze and cpu activity ceases. figure 5-18. core clock and bus clock relationship 5.4.3 clock monitor (cm) if no oscclk edges are detected within a certain time, the clock monitor within the oscillator block generates a clock monitor fail event. the crg then asserts self-clock mode or generates a system reset depending on the state of scme bit. if the clock monitor is disabled or the presence of clocks is detected no failure is indicated by the oscillator block.the clock monitor function is enabled/disabled by the cme control bit. 5.4.4 clock quality checker the clock monitor performs a coarse check on the incoming clock signal. the clock quality checker provides a more accurate check in addition to the clock monitor. a clock quality check is triggered by any of the following events: power-on reset (por) low voltage reset (lvr) wake-up from full stop mode (exit full stop) clock monitor fail indication (cm fail) a time window of 50000 vco clock cycles 1 is called check window . a number greater equal than 4096 rising oscclk edges within a check window is called osc ok . note that osc ok immediately terminates the current check window . see figure 5-19 as an example. 1. vco clock cycles are generated by the pll when running at minimum frequency f scm . core clock: bus clock / eclk chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 197 figure 5-19. check window example the sequence for clock quality check is shown in figure 5-20 . figure 5-20. sequence for clock quality check note remember that in parallel to additional actions caused by self-clock mode or clock monitor reset 1 handling the clock quality checker continues to check the oscclk signal. 1. a clock monitor reset will always set the scme bit to logical? 12 49999 50000 vco clock check window 12345 4095 4096 3 oscclk osc ok check window osc ok ? scm active? switch to oscclk exit scm clock ok num=0 num<50 ? num=num+1 yes no yes scme=1 ? no enter scm scm active? yes clock monitor reset no yes no num=50 yes no por exit full stop cm fail lv r chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 198 freescale semiconductor note the clock quality checker enables the pll and the voltage regulator (vreg) anytime a clock check has to be performed. an ongoing clock quality check could also cause a running pll (f scm ) and an active vreg during pseudo-stop mode or wait mode 5.4.5 computer operating properly watchdog (cop) figure 5-21. clock chain for cop the cop (free running watchdog timer) enables the user to check that a program is running and sequencing properly. the cop is disabled out of reset. when the cop is being used, software is responsible for keeping the cop from timing out. if the cop times out it is an indication that the software is no longer being executed in the intended sequence; thus a system reset is initiated (see section 5.5.2, ?omputer operating properly watchdog (cop) reset ).?the cop runs with a gated oscclk (see section figure 5-21., ?lock chain for cop ?. three control bits in the copctl register allow selection of seven cop time-out periods. when cop is enabled, the program must write 0x0055 and 0x00aa (in this order) to the armcop register during the selected time-out period. as soon as this is done, the cop time-out period is restarted. if the program fails to do this and the cop times out, the part will reset. also, if any value other than 0x0055 or 0x00aa is written, the part is immediately reset. windowed cop operation is enabled by setting wcop in the copctl register. in this mode, writes to the armcop register to clear the cop timer must occur in the last 25% of the selected time-out period. a premature write will immediately reset the part. if pce bit is set, the cop will continue to run in pseudo-stop mode. oscclk cr[2:0] cop timeout 0:0:0 0:0:1 0:1:0 0:1:1 1:0:0 1:0:1 1:1:0 1:1:1 4 4 2 4 2 16384 4 cr[2:0] = clock gate wait(copwai), stop( pstp, pce), cop enable gating condition chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 199 5.4.6 real-time interrupt (rti) the rti can be used to generate a hardware interrupt at a ?ed periodic rate. if enabled (by setting rtie=1), this interrupt will occur at the rate selected by the rtictl register. the rti runs with a gated oscclk (see section figure 5-22., ?lock chain for rti ?. at the end of the rti time-out period the rtif ?g is set to 1 and a new rti time-out period starts immediately. a write to the rtictl register restarts the rti time-out period. if the pre bit is set, the rti will continue to run in pseudo-stop mode. . figure 5-22. clock chain for rti 5.4.7 modes of operation 5.4.7.1 normal mode the crg block behaves as described within this speci?ation in all normal modes. 5.4.7.2 self-clock mode the vco has a minimum operating frequency, f scm . if the external clock frequency is not available due to a failure or due to long crystal start-up time, the bus clock and the core clock are derived from the vco oscclk rtr[6:4] 0:0:0 0:0:1 0:1:0 0:1:1 1:0:0 1:0:1 1:1:0 1:1:1 2 2 2 2 2 2 counter (rtr[3:0]) 4-bit modulus 1024 rti timeout = clock gate wait(rtiwai), stop( pstp, pre), rti enable gating condition chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 200 freescale semiconductor running at minimum operating frequency; this mode of operation is called self-clock mode. this requires cme = 1 and scme = 1. if the mcu was clocked by the pll clock prior to entering self-clock mode, the pllsel bit will be cleared. if the external clock signal has stabilized again, the crg will automatically select oscclk to be the system clock and return to normal mode. see section 5.4.4, ?lock quality checker ?for more information on entering and leaving self-clock mode. note in order to detect a potential clock loss, the cme bit should be always enabled (cme=1). if cme bit is disabled and the mcu is con?ured to run on pll clock (pllclk), a loss of external clock (oscclk) will not be detected and will cause the system clock to drift towards the vco s minimum frequency f scm . as soon as the external clock is available again the system clock ramps up to its pll target frequency. if the mcu is running on external clock any loss of clock will cause the system to go static. 5.4.8 low-power operation in run mode the rti can be stopped by setting the associated rate select bits to 0. the cop can be stopped by setting the associated rate select bits to 0. 5.4.9 low-power operation in wait mode the wai instruction puts the mcu in a low power consumption stand-by mode depending on setting of the individual bits in the clksel register. all individual wait mode con?uration bits can be superposed. this provides enhanced granularity in reducing the level of power consumption during wait mode. table 5-10 lists the individual con?uration bits and the parts of the mcu that are affected in wait mode. after executing the wai instruction the core requests the crg to switch mcu into wait mode. the crg then checks whether the pllwai, cwai and syswai bits are asserted (see figure 5-23 ). depending on the con?uration the crg switches the system and core clocks to oscclk by clearing the pllsel bit, disables the pll, disables the core clocks and ?ally disables the remaining system clocks. as soon as all clocks are switched off wait mode is active. table 5-10. mcu con?uration during wait mode pllwai cwai syswai rtiwai copwai roawai pll stopped core stopped stopped system stopped rti stopped cop stopped oscillator reduced 1 1 refer to oscillator block description for availability of a reduced oscillator amplitude. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 201 figure 5-23. wait mode entry/exit sequence enter wait mode pllwai=1 ? exit wait w. cmreset exit wait w. ext.reset exit wait mode enter scm exit wait mode core req s wait mode. cwai or syswai=1 ? syswai=1 ? clear pllsel, disable pll disable core clocks disable system clocks cme=1 ? int ? cm fail ? scme=1 ? scmie=1 ? continue w. normal op no no no no no no no yes yes yes yes yes no yes yes yes wait mode left due to external reset generate scm interrupt (wakeup from wait) scm=1 ? enter scm no yes chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 202 freescale semiconductor there are ve different scenarios for the crg to restart the mcu from wait mode: external reset clock monitor reset cop reset self-clock mode interrupt real-time interrupt (rti) if the mcu gets an external reset during wait mode active, the crg asynchronously restores all con?uration bits in the register space to its default settings and starts the reset generator. after completing the reset sequence processing begins by fetching the normal reset vector. wait mode is exited and the mcu is in run mode again. if the clock monitor is enabled (cme=1) the mcu is able to leave wait mode when loss of oscillator/external clock is detected by a clock monitor fail. if the scme bit is not asserted the crg generates a clock monitor fail reset (cmreset). the crg s behavior for cmreset is the same compared to external reset, but another reset vector is fetched after completion of the reset sequence. if the scme bit is asserted the crg generates a scm interrupt if enabled (scmie=1). after generating the interrupt the crg enters self-clock mode and starts the clock quality checker (see section 5.4.4, ?lock quality checker ?. then the mcu continues with normal operation.if the scm interrupt is blocked by scmie = 0, the scmif ?g will be asserted and clock quality checks will be performed but the mcu will not wake-up from wait mode. if any other interrupt source (e.g. rti) triggers exit from wait mode the mcu immediately continues with normal operation. if the pll has been powered-down during wait mode the pllsel bit is cleared and the mcu runs on oscclk after leaving wait mode. the software must manually set the pllsel bit again, in order to switch system and core clocks to the pllclk. if wait mode is entered from self-clock mode, the crg will continue to check the clock quality until clock check is successful. the pll and voltage regulator (vreg) will remain enabled. table 5-11 summarizes the outcome of a clock loss while in wait mode. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 203 table 5-11. outcome of clock loss in wait mode cme scme scmie crg actions 0 x x clock failure --> no action, clock loss not detected. 1 0 x clock failure --> crg performs clock monitor reset immediately 1 1 0 clock failure --> scenario 1: oscclk recovers prior to exiting wait mode. ?mcu remains in wait mode, ?vreg enabled, ?pll enabled, ?scm activated, ?start clock quality check, ?set scmif interrupt ?g. some time later oscclk recovers. ?cm no longer indicates a failure, ?4096 oscclk cycles later clock quality check indicates clock o.k., ?scm deactivated, ?pll disabled depending on pllwai, ?vreg remains enabled (never gets disabled in wait mode) . ?mcu remains in wait mode. s ome time later either a wakeup interrupt occurs (no scm interrupt) ?exit wait mode using oscclk as system clock (sysclk), ?continue normal operation. or an external reset is applied. ?exit wait mode using oscclk as system clock, ?start reset sequence. scenario 2: oscclk does not recover prior to exiting wait mode. ?mcu remains in wait mode, ?vreg enabled, ?pll enabled, ?scm activated, ?start clock quality check, ?set scmif interrupt ?g, ?keep performing clock quality checks (could continue in?itely) while in wait mode. s ome time later either a wakeup interrupt occurs (no scm interrupt) ?exit wait mode in scm using pll clock (f scm ) as system clock, ?continue to perform additional clock quality checks until oscclk is o.k. again. or an external reset is applied. ?exit wait mode in scm using pll clock (f scm ) as system clock, ?start reset sequence, ?continue to perform additional clock quality checks until oscclk is o.k.again. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 204 freescale semiconductor 5.4.10 low-power operation in stop mode all clocks are stopped in stop mode, dependent of the setting of the pce, pre and pstp bit. the oscillator is disabled in stop mode unless the pstp bit is set. all counters and dividers remain frozen but do not initialize. if the pre or pce bits are set, the rti or cop continues to run in pseudo-stop mode. in addition to disabling system and core clocks the crg requests other functional units of the mcu (e.g. voltage-regulator) to enter their individual power-saving modes (if available). this is the main difference between pseudo-stop mode and wait mode. after executing the stop instruction the core requests the crg to switch the mcu into stop mode. if the pllsel bit remains set when entering stop mode, the crg will switch the system and core clocks to oscclk by clearing the pllsel bit. then the crg disables the pll, disables the core clock and ?ally disables the remaining system clocks. as soon as all clocks are switched off, stop mode is active. if pseudo-stop mode (pstp = 1) is entered from self-clock mode the crg will continue to check the clock quality until clock check is successful. the pll and the voltage regulator (vreg) will remain enabled. if full stop mode (pstp = 0) is entered from self-clock mode an ongoing clock quality check will be stopped. a complete timeout window check will be started when stop mode is exited again. wake-up from stop mode also depends on the setting of the pstp bit. 1 1 1 clock failure --> ?vreg enabled, ?pll enabled, ?scm activated, ?start clock quality check, ?scmif set. scmif generates self-clock mode wakeup interrupt. ?exit wait mode in scm using pll clock (f scm ) as system clock, ?continue to perform a additional clock quality checks until oscclk is o.k. again. table 5-11. outcome of clock loss in wait mode (continued) cme scme scmie crg actions chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 205 figure 5-24. stop mode entry/exit sequence 5.4.10.1 wake-up from pseudo-stop (pstp=1) wake-up from pseudo-stop is the same as wake-up from wait mode. there are also three different scenarios for the crg to restart the mcu from pseudo-stop mode: external reset clock monitor fail wake-up interrupt exit stop w. cmreset exit stop mode enter scm exit stop mode core req s stop mode. clear pllsel, disable pll cme=1 ? int ? cm fail ? scme=1 ? scmie=1 ? continue w. normal op no no no no yes yes yes yes yes generate scm interrupt (wakeup from stop) enter stop mode exit stop w. ext.reset wait mode left due to external clock ok ? scme=1 ? enter scm yes no yes exit stop w. cmreset no no no pstp=1 ? int ? yes no yes exit stop mode exit stop mode scm=1 ? enter scm no yes chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 206 freescale semiconductor if the mcu gets an external reset during pseudo-stop mode active, the crg asynchronously restores all con?uration bits in the register space to its default settings and starts the reset generator. after completing the reset sequence processing begins by fetching the normal reset vector. pseudo-stop mode is exited and the mcu is in run mode again. if the clock monitor is enabled (cme = 1) the mcu is able to leave pseudo-stop mode when loss of oscillator/external clock is detected by a clock monitor fail. if the scme bit is not asserted the crg generates a clock monitor fail reset (cmreset). the crg s behavior for cmreset is the same compared to external reset, but another reset vector is fetched after completion of the reset sequence. if the scme bit is asserted the crg generates a scm interrupt if enabled (scmie=1). after generating the interrupt the crg enters self-clock mode and starts the clock quality checker (see section 5.4.4, ?lock quality checker ?. then the mcu continues with normal operation. if the scm interrupt is blocked by scmie = 0, the scmif ?g will be asserted but the crg will not wake-up from pseudo-stop mode. if any other interrupt source (e.g. rti) triggers exit from pseudo-stop mode the mcu immediately continues with normal operation. because the pll has been powered-down during stop mode the pllsel bit is cleared and the mcu runs on oscclk after leaving stop mode. the software must set the pllsel bit again, in order to switch system and core clocks to the pllclk. table 5-12 summarizes the outcome of a clock loss while in pseudo-stop mode. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 207 table 5-12. outcome of clock loss in pseudo-stop mode cme scme scmie crg actions 0 x x clock failure --> no action, clock loss not detected. 1 0 x clock failure --> crg performs clock monitor reset immediately 1 1 0 clock monitor failure --> scenario 1: oscclk recovers prior to exiting pseudo-stop mode. ?mcu remains in pseudo-stop mode, ?vreg enabled, ?pll enabled, ?scm activated, ?start clock quality check, ?set scmif interrupt ?g. some time later oscclk recovers. ?cm no longer indicates a failure, ?4096 oscclk cycles later clock quality check indicates clock o.k., ?scm deactivated, ?pll disabled, ?vreg disabled. ?mcu remains in pseudo-stop mode. s ome time later either a wakeup interrupt occurs (no scm interrupt) ?exit pseudo-stop mode using oscclk as system clock (sysclk), ?continue normal operation. or an external reset is applied. ?exit pseudo-stop mode using oscclk as system clock, ?start reset sequence. scenario 2: oscclk does not recover prior to exiting pseudo-stop mode. ?mcu remains in pseudo-stop mode, ?vreg enabled, ?pll enabled, ?scm activated, ?start clock quality check, ?set scmif interrupt ?g, ?keep performing clock quality checks (could continue in?itely) while in pseudo-stop mode. s ome time later either a wakeup interrupt occurs (no scm interrupt) ?exit pseudo-stop mode in scm using pll clock (f scm ) as system clock ?continue to perform additional clock quality checks until oscclk is o.k. again. or an external reset is applied. ?exit pseudo-stop mode in scm using pll clock (f scm ) as system clock ?start reset sequence, ?continue to perform additional clock quality checks until oscclk is o.k.again. chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 208 freescale semiconductor 5.4.10.2 wake-up from full stop (pstp=0) the mcu requires an external interrupt or an external reset in order to wake-up from stop mode. if the mcu gets an external reset during full stop mode active, the crg asynchronously restores all con?uration bits in the register space to its default settings and will perform a maximum of 50 clock check_windows (see section 5.4.4, ?lock quality checker ?. after completing the clock quality check the crg starts the reset generator. after completing the reset sequence processing begins by fetching the normal reset vector. full stop mode is exited and the mcu is in run mode again. if the mcu is woken-up by an interrupt, the crg will also perform a maximum of 50 clock check_window s (see section 5.4.4, ?lock quality checker ?. if the clock quality check is successful, the crg will release all system and core clocks and will continue with normal operation. if all clock checks within the timeout-window are failing, the crg will switch to self-clock mode or generate a clock monitor reset (cmreset) depending on the setting of the scme bit. because the pll has been powered-down during stop mode the pllsel bit is cleared and the mcu runs on oscclk after leaving stop mode. the software must manually set the pllsel bit again, in order to switch system and core clocks to the pllclk. note in full stop mode, the clock monitor is disabled and any loss of clock will not be detected. 5.5 resets this section describes how to reset the crg and how the crg itself controls the reset of the mcu. it explains all special reset requirements. because the reset generator for the mcu is part of the crg, this section also describes all automatic actions that occur during or as a result of individual reset conditions. the reset values of registers and signals are provided in section 5.3, ?emory map and register 1 1 1 clock failure --> ?vreg enabled, ?pll enabled, ?scm activated, ?start clock quality check, ?scmif set. scmif generates self-clock mode wakeup interrupt. ?exit pseudo-stop mode in scm using pll clock (f scm ) as system clock, ?continue to perform a additional clock quality checks until oscclk is o.k. again. table 5-12. outcome of clock loss in pseudo-stop mode (continued) cme scme scmie crg actions chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 209 de?ition . all reset sources are listed in table 5-13 . refer to the device overview chapter for related vector addresses and priorities. the reset sequence is initiated by any of the following events: low level is detected at the reset pin (external reset). power on is detected. low voltage is detected. cop watchdog times out. clock monitor failure is detected and self-clock mode was disabled (scme = 0). upon detection of any reset event, an internal circuit drives the reset pin low for 128 sysclk cycles (see figure 5-25 ). because entry into reset is asynchronous it does not require a running sysclk. however, the internal reset circuit of the crg cannot sequence out of current reset condition without a running sysclk. the number of 128 sysclk cycles might be increased by n = 3 to 6 additional sysclk cycles depending on the internal synchronization latency. after 128+n sysclk cycles the reset pin is released. the reset generator of the crg waits for additional 64 sysclk cycles and then samples the reset pin to determine the originating source. table 5-14 shows which vector will be fetched. note external circuitry connected to the reset pin should not include a large capacitance that would interfere with the ability of this signal to rise to a valid logic 1 within 64 sysclk cycles after the low drive is released. table 5-13. reset summary reset source local enable power-on reset none low voltage reset none external reset none clock monitor reset pllctl (cme=1, scme=0) cop watchdog reset copctl (cr[2:0] nonzero) table 5-14. reset vector selection sampled reset pin (64 cycles after release) clock monitor reset pending cop reset pending vector fetch 1 0 0 por / lvr / external reset 1 1 x clock monitor reset 1 0 1 cop reset 0 x x por / lvr / external reset with rise of reset pin chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 210 freescale semiconductor the internal reset of the mcu remains asserted while the reset generator completes the 192 sysclk long reset sequence. the reset generator circuitry always makes sure the internal reset is deasserted synchronously after completion of the 192 sysclk cycles. in case the reset pin is externally driven low for more than these 192 sysclk cycles (external reset), the internal reset remains asserted too. figure 5-25. reset timing 5.5.1 clock monitor reset the crg generates a clock monitor reset in case all of the following conditions are true: clock monitor is enabled (cme=1) loss of clock is detected self-clock mode is disabled (scme=0) the reset event asynchronously forces the con?uration registers to their default settings (see section 5.3, ?emory map and register de?ition ?. in detail the cme and the scme are reset to logical ? (which doesn t change the state of the cme bit, because it has already been set). as a consequence, the crg immediately enters self-clock mode and starts its internal reset sequence. in parallel the clock quality check starts. as soon as clock quality check indicates a valid oscillator clock the crg switches to oscclk and leaves self-clock mode. because the clock quality checker is running in parallel to the reset generator, the crg may leave self-clock mode while completing the internal reset sequence. when the reset sequence is ?ished the crg checks the internally latched state of the clock monitor fail circuit. if a clock monitor fail is indicated processing begins by fetching the clock monitor reset vector. 5.5.2 computer operating properly watchdog (cop) reset when cop is enabled, the crg expects sequential write of 0x0055 and 0x00aa (in this order) to the armcop register during the selected time-out period. as soon as this is done, the cop time-out period restarts. if the program fails to do this the crg will generate a reset. also, if any value other than 0x0055 or 0x00aa is written, the crg immediately generates a reset. in case windowed cop operation is enabled ) ( ) ( ) ( ) sysclk 128+ n cycles 64 cycles with n being min 3 / max 6 cycles depending on internal synchronization delay crg drives reset pin low possibly sysclk not running possibly reset driven low externally ) ( ( reset reset pin released chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 211 writes (0x0055 or 0x00aa) to the armcop register must occur in the last 25% of the selected time-out period. a premature write the crg will immediately generate a reset. as soon as the reset sequence is completed the reset generator checks the reset condition. if no clock monitor failure is indicated and the latched state of the cop timeout is true, processing begins by fetching the cop vector. 5.5.3 power-on reset, low voltage reset the on-chip voltage regulator detects when v dd to the mcu has reached a certain level and asserts power-on reset or low voltage reset or both. as soon as a power-on reset or low voltage reset is triggered the crg performs a quality check on the incoming clock signal. as soon as clock quality check indicates a valid oscillator clock signal the reset sequence starts using the oscillator clock. if after 50 check windows the clock quality check indicated a non-valid oscillator clock the reset sequence starts using self-clock mode. figure 5-26 and figure 5-27 show the power-up sequence for cases when the reset pin is tied to v dd and when the reset pin is held low. figure 5-26. reset pin tied to v dd (by a pull-up resistor) figure 5-27. reset pin held low externally reset internal por 128 sysclk 64 sysclk internal reset clock quality check (no self-clock mode) ) ( ) ( ) ( clock quality check reset internal por internal reset 128 sysclk 64 sysclk (no self-clock mode) ) ( ) ( ) ( chapter 5 clocks and reset generator (crgv4) mc9s12kg128 data sheet, rev. 1.15 212 freescale semiconductor 5.6 interrupts the interrupts/reset vectors requested by the crg are listed in table 5-15 . refer to the device overview chapter for related vector addresses and priorities. 5.6.1 real-time interrupt the crg generates a real-time interrupt when the selected interrupt time period elapses. rti interrupts are locally disabled by setting the rtie bit to 0. the real-time interrupt ?g (rtif) is set to 1 when a timeout occurs, and is cleared to 0 by writing a 1 to the rtif bit. the rti continues to run during pseudo-stop mode if the pre bit is set to 1. this feature can be used for periodic wakeup from pseudo-stop if the rti interrupt is enabled. 5.6.2 pll lock interrupt the crg generates a pll lock interrupt when the lock condition of the pll has changed, either from a locked state to an unlocked state or vice versa. lock interrupts are locally disabled by setting the lockie bit to 0. the pll lock interrupt ?g (lockif) is set to1 when the lock condition has changed, and is cleared to 0 by writing a 1 to the lockif bit. 5.6.3 self-clock mode interrupt the crg generates a self-clock mode interrupt when the scm condition of the system has changed, either entered or exited self-clock mode. scm conditions can only change if the self-clock mode enable bit (scme) is set to 1. scm conditions are caused by a failing clock quality check after power-on reset (por) or low voltage reset (lvr) or recovery from full stop mode (pstp = 0) or clock monitor failure. for details on the clock quality check refer to section 5.4.4, ?lock quality checker . if the clock monitor is enabled (cme = 1) a loss of external clock will also cause a scm condition (scme = 1). scm interrupts are locally disabled by setting the scmie bit to 0. the scm interrupt ?g (scmif) is set to 1 when the scm condition has changed, and is cleared to 0 by writing a 1 to the scmif bit. table 5-15. crg interrupt vectors interrupt source ccr mask local enable real-time interrupt i bit crgint (rtie) lock interrupt i bit crgint (lockie) scm interrupt i bit crgint (scmie) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 213 chapter 6 pierce oscillator (s12osclcpv1) 6.1 introduction the pierce oscillator (xosc) module provides a robust, low-noise and low-power clock source. the module will be operated from the v ddpll supply rail (2.5 v nominal) and require the minimum number of external components. it is designed for optimal start-up margin with typical crystal oscillators. 6.1.1 features the xosc will contain circuitry to dynamically control current gain in the output amplitude. this ensures a signal with low harmonic distortion, low power and good noise immunity. high noise immunity due to input hysteresis low rf emissions with peak-to-peak swing limited dynamically transconductance (gm) sized for optimum start-up margin for typical oscillators dynamic gain control eliminates the need for external current limiting resistor integrated resistor eliminates the need for external bias resistor low power consumption: operates from 2.5 v (nominal) supply amplitude control limits power clock monitor 6.1.2 modes of operation two modes of operation exist: 1. loop controlled pierce oscillator 2. external square wave mode featuring also full swing pierce without internal feedback resistor chapter 6 pierce oscillator (s12osclcpv1) mc9s12kg128 data sheet, rev. 1.15 214 freescale semiconductor 6.1.3 block diagram figure 6-1 shows a block diagram of the xosc. figure 6-1. xosc block diagram 6.2 external signal description this section lists and describes the signals that connect off chip 6.2.1 v ddpll and v sspll ?operating and ground voltage pins theses pins provides operating voltage (v ddpll ) and ground (v sspll ) for the xosc circuitry. this allows the supply voltage to the xosc to be independently bypassed. 6.2.2 extal and xtal ?input and output pins these pins provide the interface for either a crystal or a cmos compatible clock to control the internal clock generator circuitry. extal is the external clock input or the input to the crystal oscillator ampli?r. xtal is the output of the crystal oscillator ampli?r. the mcu internal system clock is derived from the extal xtal gain control v ddpll = 2.5 v rf oscclk monitor_failure clock monitor peak detector chapter 6 pierce oscillator (s12osclcpv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 215 extal input frequency. in full stop mode (pstp = 0), the extal pin is pulled down by an internal resistor of typical 200 k ? . note freescale recommends an evaluation of the application board and chosen resonator or crystal by the resonator or crystal supplier. loop controlled circuit is not suited for overtone resonators and crystals. figure 6-2. loop controlled pierce oscillator connections (xclks = 0) note full swing pierce circuit is not suited for overtone resonators and crystals without a careful component selection. figure 6-3. full swing pierce oscillator connections (xclks = 1) figure 6-4. external clock connections (xclks = 1) mcu extal xtal v sspll crystal or ceramic resonator c2 c1 * r s can be zero (shorted) when use with higher frequency crystals. refer to manufacturer? data. mcu extal xtal rs* rb v sspll crystal or ceramic resonator c2 c1 mcu extal xtal not connected cmos compatible external oscillator (v ddpll level) chapter 6 pierce oscillator (s12osclcpv1) mc9s12kg128 data sheet, rev. 1.15 216 freescale semiconductor 6.2.3 xclks ?input signal the xclks is an input signal which controls whether a crystal in combination with the internal loop controlled (low power) pierce oscillator is used or whether full swing pierce oscillator/external clock circuitry is used. refer to the device overview chapter for polarity and sampling conditions of the xclks pin. table 6-1 lists the state coding of the sampled xclks signal. . 6.3 memory map and register de?ition the crg contains the registers and associated bits for controlling and monitoring the oscillator module. 6.4 functional description the xosc module has control circuitry to maintain the crystal oscillator circuit voltage level to an optimal level which is determined by the amount of hysteresis being used and the maximum oscillation range. the oscillator block has two external pins, extal and xtal. the oscillator input pin, extal, is intended to be connected to either a crystal or an external clock source. the selection of loop controlled pierce oscillator or full swing pierce oscillator/external clock depends on the xclks signal which is sampled during reset. the xtal pin is an output signal that provides crystal circuit feedback. a buffered extal signal becomes the internal clock. to improve noise immunity, the oscillator is powered by the v ddpll and v sspll power supply pins. 6.4.1 gain control a closed loop control system will be utilized whereby the ampli?r is modulated to keep the output waveform sinusoidal and to limit the oscillation amplitude. the output peak to peak voltage will be kept above twice the maximum hysteresis level of the input buffer. electrical speci?ation details are provided in the electrical characteristics appendix. 6.4.2 clock monitor the clock monitor circuit is based on an internal rc time delay so that it can operate without any mcu clocks. if no oscclk edges are detected within this rc time delay, the clock monitor indicates failure which asserts self-clock mode or generates a system reset depending on the state of scme bit. if the clock monitor is disabled or the presence of clocks is detected no failure is indicated.the clock monitor function is enabled/disabled by the cme control bit, described in the crg block description chapter. table 6-1. clock selection based on xclks xclks description 0 loop controlled pierce oscillator selected 1 full swing pierce oscillator/external clock selected chapter 6 pierce oscillator (s12osclcpv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 217 6.4.3 wait mode operation during wait mode, xosc is not impacted. 6.4.4 stop mode operation xosc is placed in a static state when the part is in stop mode except when pseudo-stop mode is enabled. during pseudo-stop mode, xosc is not impacted. chapter 6 pierce oscillator (s12osclcpv1) mc9s12kg128 data sheet, rev. 1.15 218 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 219 chapter 7 analog-to-digital converter (atd10b16cv1) 7.1 introduction the atd is an 16-channel, 10-bit, multiplexed input successive approximation analog-to-digital converter. refer to device electrical speci?ations for atd accuracy. the block is designed to be upwards compatible with the 68hc11 standard 10/8-bit a/d converter. in addition, there are new operating modes that are unique to the hc12 design. 7.1.1 features 8/10-bit resolution. ? s, 10-bit single conversion time. sample buffer ampli?r. programmable sample time. left/right justi?d, signed/unsigned result data. external trigger control. conversion completion interrupt generation. analog input multiplexer for 16 analog input channels. analog/digital input pin multiplexing. 1-to-16 conversion sequence lengths. continuous conversion mode. multiple channel scans. con?urable external trigger functionality on any atd channel. con?urable location for channel wrap around (when converting multiple channels in a sequence). chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 220 freescale semiconductor 7.1.2 block diagram figure 7-1. atd block diagram vrl an8 / pad8 at d port ad data registers analog mux mode and timing control successive appr0ximation register (sar) results atd 0 atd 1 atd 2 atd 3 atd 4 atd 5 atd 6 atd 7 and dac sample and hold 1 1 vrh vssa vdda conversion complete interrupt + comparator clock prescaler bus clock atd clock atd input enable registers atd 8 atd 9 atd 10 atd 11 atd 12 atd 13 atd 14 atd 15 an7 / pad7 an6 / pad6 an5 / pad5 an4 / pad4 an3 / pad3 an2 / pad2 an1 / pad1 an0 / pad0 an9 / pad9 an10 / pad10 an11 / pad11 an12 / pad12 an13 / pad13 an14 / pad14 an15 / pad15 etrig (see device speci?ation for availablity) chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 221 7.1.3 modes of operation 7.1.3.1 conversion modes there is software programmable selection between performing single or continuous conversion on a single channel or multiple channels . 7.1.3.2 mcu operating modes stop mode entering stop mode causes all clocks to halt and thus the system is placed in a minimum power standby mode. this halts any conversion sequence in progress. during recovery from stop mode, there must be a minimum delay for the stop recovery time t sr before initiating a new atd conversion sequence. wait mode entering wait mode the atd conversion either continues or halts for low power depending on the logical value of the await bit. freeze mode in freeze mode the atd will behave according to the logical values of the frz1 and frz0 bits. this is useful for debugging and emulation. 7.2 signal description the atd has a total of 21 external pins. 7.2.1 detailed signal descriptions 7.2.1.1 an x / pad x ( x = 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1, 0) this pin serves as the analog input channel x . it can also be con?ured as general purpose digital input and/or external trigger for the atd conversion. 7.2.1.2 etrig this pin can be con?ured to serve as an external trigger for the atd conversion. refer to device speci?ation for availability and connectivity of this pin. 7.2.1.3 vrh, vrl vrh is the high reference voltage, vrl is the low reference voltage for atd conversion. 7.2.1.4 vdda, vssa these pins are the power supplies for the analog circuitry of the atd10b16c block. chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 222 freescale semiconductor 7.3 memory map and register de?ition this section provides a detailed description of all registers accessible in the atd. 7.3.1 module memory map figure 7-2 gives an overview of all atd registers address name bit 7 6 5 4 3 2 1 bit 0 0x0000 atdctl0 r0 0 0 0 wrap3 wrap2 wrap1 wrap0 w 0x0001 atdctl1 r etrigsel 000 etrigch3 etrigch2 etrigch1 etrigch0 w 0x0002 atdctl2 r adpu affc awai etrigle etrigp etrige ascie ascif w 0x0003 atdctl3 r0 s8c s4c s2c s1c fifo frz1 frz0 w 0x0004 atdctl4 r sres8 smp1 smp0 prs4 prs3 prs2 prs1 prs0 w 0x0005 atdctl5 r djm dsgn scan mult cd cc cb ca w 0x0006 atdstat0 r scf 0 etorf fifor cc3 cc2 cc1 cc0 w 0x0007 unimplemented r w 0x0008 atdtest0 1 ruuuuuuuu w 1 atdtest0 is intended for factory test purposes only. 0x0009 atdtest1 ruu00000 sc w 0x000a atdstat2 r ccf15 ccf14 ccf13 ccf12 ccf11 ccf10 ccf9 ccf8 w 0x000b atdstat1 r ccf7 ccf6 ccf5 ccf4 ccf3 ccf2 ccf1 ccf0 w 0x000c atddien0 r ien15 ien14 ien13 ien12 ien11 ien10 ien9 ien8 w 0x000d atddoen1 r ien7 ien6 ien5 ien4 ien3 ien2 ien1 ien0 w 0x000e portad0 r ptad15 ptad14 ptad13 ptad12 ptad11 ptad10 ptad9 ptad8 w = unimplemented or reserved figure 7-2. atd register summary (sheet 1 of 3) chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 223 0x000f portad1 r ptad7 ptad6 ptad5 ptad4 ptad3 ptad2 ptad1 ptad0 w 0x0010 atddr0h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0011 atddr0l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0012 atddr1h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0013 atddr1l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0014 atddr2h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0015 atddr2l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0016 atddr3h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0017 atddr3l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0018 atddr4h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0019 atddr4l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x001a atddr5h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x001b atddr5l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x001c atddr6h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x001d atddr6l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x001e atddr7h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x001f atddr7l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0020 atddr8h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0021 atddr8l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w address name bit 7 6 5 4 3 2 1 bit 0 = unimplemented or reserved figure 7-2. atd register summary (sheet 2 of 3) chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 224 freescale semiconductor note register address = base address + address offset, where the base address is de?ed at the mcu level and the address offset is de?ed at the module level. 0x0022 atddr9h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0023 atddr9l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0024 atddr10h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0025 atddr10l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0026 atddr11h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0027 atddr11l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0028 atddr12h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x0029 atddr12l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x002a atddr13h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x002b atddr13l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x002c atddr14h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x002d atddr14l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x002e atddr15h r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w 0x002f atddr15l r see section 7.3.2.16.1, ?eft justi?d result data and section 7.3.2.16.2, ?ight justi?d result data w address name bit 7 6 5 4 3 2 1 bit 0 = unimplemented or reserved figure 7-2. atd register summary (sheet 3 of 3) chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 225 7.3.2 register descriptions this section describes in address order all the atd registers and their individual bits. 7.3.2.1 atd control register 0 (atdctl0) writes to this register will abort current conversion sequence but will not start a new sequence. read: anytime write: anytime module base + 0x0000 76543210 r0000 wrap3 wrap2 wrap1 wrap0 w reset 0 0 0 01111 = unimplemented or reserved figure 7-3. atd control register 0 (atdctl0) table 7-1. atdctl0 field descriptions field description 3? wrap[3:0] wrap around channel select bits ?these bits determine the channel for wrap around when doing multi-channel conversions. the coding is summarized in table 7-2 . table 7-2. multi-channel wrap around coding wrap3 wrap2 wrap1 wrap0 multiple channel conversions (mult = 1) wrap around to an0/pad0 after converting 0 0 0 0 reserved 0 0 0 1 an1 / pad1 0 0 1 0 an2 / pad2 0 0 1 1 an3 / pad3 0 1 0 0 an4 / pad4 0 1 0 1 an5 / pad5 0 1 1 0 an6 / pad6 0 1 1 1 an7 / pad7 1 0 0 0 an8 / pad8 1 0 0 1 an9 / pad9 1 0 1 0 an10 / pad10 1 0 1 1 an11 / pad11 1 1 0 0 an12 / pad12 1 1 0 1 an13 / pad13 1 1 1 0 an14 / pad14 1 1 1 1 an15 / pad15 chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 226 freescale semiconductor 7.3.2.2 atd control register 1 (atdctl1) writes to this register will abort current conversion sequence but will not start a new sequence. read: anytime write: anytime module base + 0x0001 76543210 r etrigsel 000 etrigch3 etrigch2 etrigch1 etrigch0 w reset 0 0 0 01111 = unimplemented or reserved figure 7-4. atd control register 1 (atdctl1) table 7-3. atdctl1 field descriptions field description 7 etrigsel external trigger source select ?this bit selects the external trigger source to be either one of the ad channels or a speci? port pin etrig. see device speci?ation for availability and connectivity of etrig pin. if etrig pin option is not available, writing a 1 to etrisel only sets the bit but has not effect, that means still one of the ad channels (selected by etrigch3-0) is the source for external trigger. 0 external trigger source is the ad channel selected by etrigch3-0 (see table 7-4 ). 1 external trigger source is etrig pin. 3? etrigch[3:0] external trigger channel select ?if etrigsel = 0 then these bits select one of the ad channels as the source for external trigger. the coding is summarized table 7-4 . table 7-4. external trigger channel select coding etrigsel etrigch3 etrigch2 etrigch1 etrigch0 external trigger source 0 0 0 0 0 an0 / pad0 0 0 0 0 1 an1 / pad1 0 0 0 1 0 an2 / pad2 0 0 0 1 1 an3 / pad3 0 0 1 0 0 an4 / pad4 0 0 1 0 1 an5 / pad5 0 0 1 1 0 an6 / pad6 0 0 1 1 1 an7 / pad7 0 1 0 0 0 an8 / pad8 0 1 0 0 1 an9 / pad9 0 1 0 1 0 an10 / pad10 0 1 0 1 1 an11 / pad11 0 1 1 0 0 an12 / pad12 0 1 1 0 1 an13 / pad13 0 1 1 1 0 an14 / pad14 0 1 1 1 1 an15 / pad15 1 x x x x etrig 1 1 only if etrig pin option available (see device speci?ation), else external trigger source is still on one of the ad channels selected by etrigch3? chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 227 7.3.2.3 atd control register 2 (atdctl2) this register controls power down, interrupt and external trigger. writes to this register will abort current conversion sequence but will not start a new sequence. read: anytime write: anytime module base + 0x0002 76543210 r adpu affc awai etrigle etrigp etrige ascie ascif w reset 0 0 0 00000 = unimplemented or reserved figure 7-5. atd control register 2 (atdctl2) table 7-5. atdctl2 field descriptions field description 7 adpu atd power dow n ?this bit provides on/off control over the atd block allowing reduced mcu power consumption. because analog electronic is turned off when powered down, the atd requires a recovery time period after adpu bit is enabled. 0 power down atd 1 normal atd functionality 6 affc atd fast flag clear all 0 atd ?g clearing operates normally (read the status register atdstat1 before reading the result register to clear the associate ccf ?g). 1 changes all atd conversion complete ?gs to a fast clear sequence. any access to a result register will cause the associate ccf ?g to clear automatically. 5 awai atd power down in wait mode when entering wait mode this bit provides on/off control over the atd block allowing reduced mcu power. because analog electronic is turned off when powered down, the atd requires a recovery time period after exit from wait mode. 0 atd continues to run in wait mode 1 halt conversion and power down atd during wait mode after exiting wait mode with an interrupt conversion will resume. but due to the recovery time the result of this conversion should be ignored. 4 etrigle external trigger level/edge control ?this bit controls the sensitivity of the external trigger signal. see table 7-6 for details. 3 etrigp external trigger polarity this bit controls the polarity of the external trigger signal. see table 7-6 for details. 2 etrige external trigger mode enable this bit enables the external trigger on etrig pin or one of the atd channels as described in table 7-4 . if external trigger source is one the atd channels, the digital input buffer of this channel is enabled. the external trigger allows to synchronize sample and atd conversions processes with external events. 0 disable external trigger 1 enable external trigger note: if using one of the atd channel as external trigger (etrigsel = 0) the conversion results for this channel have no meaning while external trigger mode is enabled. chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 228 freescale semiconductor 7.3.2.4 atd control register 3 (atdctl3) this register controls the conversion sequence length, fifo for results registers and behavior in freeze mode. writes to this register will abort current conversion sequence but will not start a new sequence. read: anytime write: anytime 1 ascie atd sequence complete interrupt enable 0 atd sequence complete interrupt requests are disabled. 1 atd interrupt will be requested whenever ascif = 1 is set. 0 ascif atd sequence complete interrupt flag ?if ascie = 1 the ascif ?g equals the scf ?g (see section 7.3.2.7, ?td status register 0 (atdstat0) ), else ascif reads zero. writes have no effect. 0 no atd interrupt occurred 1 atd sequence complete interrupt pending table 7-6. external trigger con?urations etrigle etrigp external trigger sensitivity 0 0 falling edge 0 1 rising edge 1 0 low level 1 1 high level module base + 0x0003 76543210 r0 s8c s4c s2c s1c fifo frz1 frz0 w reset 0 0 1 00000 = unimplemented or reserved figure 7-6. atd control register 3 (atdctl3) table 7-7. atdctl3 field descriptions field description 6? s8c, s4c, s2c, s1c conversion sequence length these bits control the number of conversions per sequence. table 7-8 shows all combinations. at reset, s4c is set to 1 (sequence length is 4). this is to maintain software continuity to hc12 family. table 7-5. atdctl2 field descriptions (continued) field description chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 229 2 fifo result register fifo mode if this bit is zero (non-fifo mode), the a/d conversion results map into the result registers based on the conversion sequence; the result of the ?st conversion appears in the ?st result register, the second result in the second result register, and so on. if this bit is one (fifo mode) the conversion counter is not reset at the beginning or ending of a conversion sequence; conversion results are placed in consecutive result registers between sequences. the result register counter wraps around when it reaches the end of the result register ?e. the conversion counter value in atdstat0 can be used to determine where in the result register ?e, the current conversion result will be placed. finally, which result registers hold valid data can be tracked using the conversion complete ?gs. fast ?g clear mode may or may not be useful in a particular application to track valid data. 0 conversion results are placed in the corresponding result register up to the selected sequence length. 1 conversion results are placed in consecutive result registers (wrap around at end). 1? frz[1:0] background debug freeze enable ?when debugging an application, it is useful in many cases to have the atd pause when a breakpoint (freeze mode) is encountered. these 2 bits determine how the atd will respond to a breakpoint as shown in table 7-9 . leakage onto the storage node and comparator reference capacitors may compromise the accuracy of an immediately frozen conversion depending on the length of the freeze period. table 7-8. conversion sequence length coding s8c s4c s2c s1c number of conversions per sequence 0000 16 0001 1 0010 2 0011 3 0100 4 0101 5 0110 6 0111 7 1000 8 1001 9 1010 10 1011 11 1100 12 1101 13 1110 14 1111 15 table 7-9. atd behavior in freeze mode (breakpoint) frz1 frz0 behavior in freeze mode 0 0 continue conversion 0 1 reserved 1 0 finish current conversion, then freeze 1 1 freeze immediately table 7-7. atdctl3 field descriptions (continued) field description chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 230 freescale semiconductor 7.3.2.5 atd control register 4 (atdctl4) this register selects the conversion clock frequency, the length of the second phase of the sample time and the resolution of the a/d conversion (i.e., 8-bits or 10-bits). writes to this register will abort current conversion sequence but will not start a new sequence. read: anytime write: anytime module base + 0x0004 76543210 r sres8 smp1 smp0 prs4 prs3 prs2 prs1 prs0 w reset 0 0 0 00101 figure 7-7. atd control register 4 (atdctl4) table 7-10. atdctl4 field descriptions field description 7 sres8 a/d resolution select this bit selects the resolution of a/d conversion results as either 8 or 10 bits. the a/d converter has an accuracy of 10 bits. however, if low resolution is required, the conversion can be speeded up by selecting 8-bit resolution. 0 10-bit resolution 1 8-bit resolution 6? smp[1:0] sample time select these two bits select the length of the second phase of the sample time in units of atd conversion clock cycles. note that the atd conversion clock period is itself a function of the prescaler value (bits prs4?). the sample time consists of two phases. the ?st phase is two atd conversion clock cycles long and transfers the sample quickly (via the buffer ampli?r) onto the a/d machine s storage node. the second phase attaches the external analog signal directly to the storage node for ?al charging and high accuracy. table 7-11 lists the lengths available for the second sample phase. 4? prs[4:0] atd clock prescaler ?hese 5 bits are the binary value prescaler value prs. the atd conversion clock frequency is calculated as follows: note: the maximum atd conversion clock frequency is half the bus clock. the default (after reset) prescaler value is 5 which results in a default atd conversion clock frequency that is bus clock divided by 12. table 7-12 illustrates the divide-by operation and the appropriate range of the bus clock. table 7-11. sample time select smp1 smp0 length of 2nd phase of sample time 0 0 2 a/d conversion clock periods 0 1 4 a/d conversion clock periods 1 0 8 a/d conversion clock periods 1 1 16 a/d conversion clock periods atdclock busclock [] prs 1 + [] -------------------------------- 0.5 = chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 231 table 7-12. clock prescaler values prescale value total divisor value maximum bus clock 1 1 maximum atd conversion clock frequency is 2 mhz. the maximum allowed bus clock frequency is shown in this column. minimum bus clock 2 2 minimum atd conversion clock frequency is 500 khz. the minimum allowed bus clock frequency is shown in this column. 00000 00001 00010 00011 00100 00101 00110 00111 01000 01001 01010 01011 01100 01101 01110 01111 10000 10001 10010 10011 10100 10101 10110 10111 11000 11001 11010 11011 11100 11101 11110 11111 divide by 2 divide by 4 divide by 6 divide by 8 divide by 10 divide by 12 divide by 14 divide by 16 divide by 18 divide by 20 divide by 22 divide by 24 divide by 26 divide by 28 divide by 30 divide by 32 divide by 34 divide by 36 divide by 38 divide by 40 divide by 42 divide by 44 divide by 46 divide by 48 divide by 50 divide by 52 divide by 54 divide by 56 divide by 58 divide by 60 divide by 62 divide by 64 4 mhz 8 mhz 12 mhz 16 mhz 20 mhz 24 mhz 28 mhz 32 mhz 36 mhz 40 mhz 44 mhz 48 mhz 52 mhz 56 mhz 60 mhz 64 mhz 68 mhz 72 mhz 76 mhz 80 mhz 84 mhz 88 mhz 92 mhz 96 mhz 100 mhz 104 mhz 108 mhz 112 mhz 116 mhz 120 mhz 124 mhz 128 mhz 1 mhz 2 mhz 3 mhz 4 mhz 5 mhz 6 mhz 7 mhz 8 mhz 9 mhz 10 mhz 11 mhz 12 mhz 13 mhz 14 mhz 15 mhz 16 mhz 17 mhz 18 mhz 19 mhz 20 mhz 21 mhz 22 mhz 23 mhz 24 mhz 25 mhz 26 mhz 27 mhz 28 mhz 29 mhz 30 mhz 31 mhz 32 mhz chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 232 freescale semiconductor 7.3.2.6 atd control register 5 (atdctl5) this register selects the type of conversion sequence and the analog input channels sampled. writes to this register will abort current conversion sequence and start a new conversion sequence. read: anytime write: anytime module base + 0x0005 76543210 r djm dsgn scan mult cd cc cb ca w reset 0 0 0 00000 figure 7-8. atd control register 5 (atdctl5) table 7-13. atdctl5 field descriptions field description 7 djm result register data justi?ation ?this bit controls justi?ation of conversion data in the result registers. see section 7.3.2.16, ?td conversion result registers (atddrx) for details. 0 left justi?d data in the result registers. 1 right justi?d data in the result registers. 6 dsgn result register data signed or unsigned representation this bit selects between signed and unsigned conversion data representation in the result registers. signed data is represented as 2 s complement. signed data is not available in right justi?ation. see section 7.3.2.16, ?td conversion result registers (atddrx) for details. 0 unsigned data representation in the result registers. 1 signed data representation in the result registers. table 7-14 summarizes the result data formats available and how they are set up using the control bits. table 7-15 illustrates the difference between the signed and unsigned, left justi?d output codes for an input signal range between 0 and 5.12 volts. 5 scan continuous conversion sequence mode ?this bit selects whether conversion sequences are performed continuously or only once. 0 single conversion sequence 1 continuous conversion sequences (scan mode) 4 mult multi-channel sample mode when mult is 0, the atd sequence controller samples only from the speci?d analog input channel for an entire conversion sequence. the analog channel is selected by channel selection code (control bits cc/cb/ca located in atdctl5). when mult is 1, the atd sequence controller samples across channels. the number of channels sampled is determined by the sequence length value (s8c, s4c, s2c, s1c). the ?st analog channel examined is determined by channel selection code (cc, cb, ca control bits); subsequent channels sampled in the sequence are determined by incrementing the channel selection code or wrapping around to an0 (channel 0. 0 sample only one channel 1 sample across several channels chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 233 3? cd, cc, cb, ca analog input channel select code ?these bits select the analog input channel(s) whose signals are sampled and converted to digital codes. table 7-16 lists the coding used to select the various analog input channels. in the case of single channel conversions (mult = 0), this selection code speci?d the channel to be examined. in the case of multiple channel conversions (mult = 1), this selection code represents the ?st channel to be examined in the conversion sequence. subsequent channels are determined by incrementing the channel selection code or wrapping around to an0 (after converting the channel de?ed by the wrap around channel select bits wrap3-0 in atdctl0). in case starting with a channel number higher than the one de?ed by wrap3? the ?st wrap around will be an15 to an0. table 7-14. available result data formats sres8 djm dsgn result data formats description and bus bit mapping 1 1 1 0 0 0 0 0 1 0 0 1 0 1 x 0 1 x 8-bit / left justi?d / unsigned ?bits 8?5 8-bit / left justi?d / signed ?bits 8?5 8-bit / right justi?d / unsigned ?bits 0? 10-bit / left justi?d / unsigned ?bits 6?5 10-bit / left justi?d / signed ?bits 6?5 10-bit / right justi?d / unsigned ?bits 0? table 7-15. left justi?d, signed and unsigned atd output codes input signal vrl = 0 volts vrh = 5.12 volts signed 8-bit codes unsigned 8-bit codes signed 10-bit codes unsigned 10-bit codes 5.120 volts 5.100 volts 5.080 volts 2.580 volts 2.560 volts 2.540 volts 0.020 volts 0.000 volts 7f 7f 7e 01 00 ff 81 80 ff ff fe 81 80 7f 01 00 7fc0 7f00 7e00 0100 0000 ff00 8100 8000 ffc0 ff00 fe00 8100 8000 7f00 0100 0000 table 7-16. analog input channel select coding cd cc cb ca analog input channel 0 0 0 0 an0 0 0 0 1 an1 0 0 1 0 an2 0 0 1 1 an3 0 1 0 0 an4 0 1 0 1 an5 table 7-13. atdctl5 field descriptions (continued) field description chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 234 freescale semiconductor 7.3.2.7 atd status register 0 (atdstat0) this read-only register contains the sequence complete flag, overrun ?gs for external trigger and fifo mode, and the conversion counter. read: anytime write: anytime (no effect on cc3, cc2, cc1, cc0) 0 1 1 0 an6 0 1 1 1 an7 1 0 0 0 an8 1 0 0 1 an9 1 0 1 0 an10 1 0 1 1 an11 1 1 0 0 an12 1 1 0 1 an13 1 1 1 0 an14 1 1 1 1 an15 module base + 0x0006 76543210 r scf 0 etorf fifor cc3 cc2 cc1 cc0 w reset 0 0 0 00000 = unimplemented or reserved figure 7-9. atd status register 0 (atdstat0) table 7-17. atdstat0 field descriptions field description 7 scf sequence complete flag ?this ?g is set upon completion of a conversion sequence. if conversion sequences are continuously performed (scan = 1), the ?g is set after each one is completed. this ?g is cleared when one of the following occurs: a) write ??to scf b) write to atdctl5 (a new conversion sequence is started) c) if affc = 1 and read of a result register 0 conversion sequence not completed 1 conversion sequence has completed table 7-16. analog input channel select coding (continued) cd cc cb ca analog input channel chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 235 7.3.2.8 reserved register (atdtest0) read: anytime, returns unpredictable values write: anytime in special modes, unimplemented in normal modes note writing to this registers when in special modes can alter functionality. 5 etorf external trigger overrun flag ?while in edge trigger mode (etrigle = 0), if additional active edges are detected while a conversion sequence is in process the overrun ?g is set. this ?g is cleared when one of the following occurs: a) write ??to etorf b) write to atdctl0,1,2,3,4 (a conversion sequence is aborted) c) write to atdctl5 (a new conversion sequence is started) 0 no external trigger over run error has occurred 1 external trigger over run error has occurred 4 fifor fifo over run flag ?this bit indicates that a result register has been written to before its associated conversion complete ?g (ccf) has been cleared. this ?g is most useful when using the fifo mode because the ?g potentially indicates that result registers are out of sync with the input channels. however, it is also practical for non-fifo modes, and indicates that a result register has been over written before it has been read (i.e., the old data has been lost). this ?g is cleared when one of the following occurs: a) write ??to fifor b) start a new conversion sequence (write to atdctl5 or external trigger) 0 no over run has occurred 1 overrun condition exists (result register has been written while associated ccfx ?g was still set) 3? cc[3:0] conversion counter these 4 read-only bits are the binary value of the conversion counter. the conversion counter points to the result register that will receive the result of the current conversion. e.g. cc3 = 0, cc2 = 1, cc1 = 1, cc0 = 0 indicates that the result of the current conversion will be in atd result register 6. if in non-fifo mode (fifo = 0) the conversion counter is initialized to zero at the begin and end of the conversion sequence. if in fifo mode (fifo = 1) the register counter is not initialized. the conversion counters wraps around when its maximum value is reached. module base + 0x0008 76543210 ruuuuuuuu w reset 1 0 0 00000 = unimplemented or reserved figure 7-10. reserved register (atdtest0) table 7-17. atdstat0 field descriptions (continued) field description chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 236 freescale semiconductor 7.3.2.9 atd test register 1 (atdtest1) this register contains the sc bit used to enable special channel conversions. read: anytime, returns unpredictable values for bit7 and bit6 write: anytime note writing to this registers when in special modes can alter functionality. module base + 0x0009 76543210 ruu00000 sc w reset 0 0 0 00000 = unimplemented or reserved figure 7-11. atd test register 1 (atdtest1) table 7-18. atdtest1 field descriptions field description 0 sc special channel conversion bit if this bit is set, then special channel conversion can be selected using cc, cb and ca of atdctl5. table 7-19 lists the coding. 0 special channel conversions disabled 1 special channel conversions enabled table 7-19. special channel select coding sc cd cc cb ca analog input channel 1 0 0 x x reserved 10100 v rh 10101 v rl 10110 (v rh +v rl ) / 2 10111 reserved 1 1 x x x reserved chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 237 7.3.2.10 atd status register 2 (atdstat2) this read-only register contains the conversion complete flags ccf15 to ccf8. read: anytime write: anytime, no effect module base + 0x000a 76543210 r ccf15 ccf14 ccf13 ccf12 ccf11 ccf10 ccf9 ccf8 w reset 0 0 0 00000 = unimplemented or reserved figure 7-12. atd status register 2 (atdstat2) table 7-20. atdstat2 field descriptions field description 7? ccf[15:8] conversion complete flag x (x = 15, 14, 13, 12, 11, 10, 9, 8) ?a conversion complete ?g is set at the end of each conversion in a conversion sequence. the ?gs are associated with the conversion position in a sequence (and also the result register number). therefore, ccf8 is set when the ninth conversion in a sequence is complete and the result is available in result register atddr8; ccf9 is set when the tenth conversion in a sequence is complete and the result is available in atddr9, and so forth. a ?g ccfx (x = 15, 14, 13, 12, 11, 10, 9, 8) is cleared when one of the following occurs: a) write to atdctl5 (a new conversion sequence is started) b) if affc = 0 and read of atdstat2 followed by read of result register atddrx c) if affc = 1 and read of result register atddrx 0 conversion number x not completed 1 conversion number x has completed, result ready in atddrx chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 238 freescale semiconductor 7.3.2.11 atd status register 1 (atdstat1) this read-only register contains the conversion complete flags ccf7 to ccf0. read: anytime write: anytime, no effect module base + 0x000b 76543210 r ccf7 ccf6 ccf5 ccf4 ccf3 ccf2 ccf1 ccf0 w reset 0 0 0 00000 = unimplemented or reserved figure 7-13. atd status register 1 (atdstat1) table 7-21. atdstat1 field descriptions field description 7? ccf[7:0] conversion complete flag x (x = 7, 6, 5, 4, 3, 2, 1, 0) a conversion complete ?g is set at the end of each conversion in a conversion sequence. the ?gs are associated with the conversion position in a sequence (and also the result register number). therefore, ccf0 is set when the ?st conversion in a sequence is complete and the result is available in result register atddr0; ccf1 is set when the second conversion in a sequence is complete and the result is available in atddr1, and so forth. a ?g ccfx (x = 7, 6, 5, 4, 3, 2, 1, 0) is cleared when one of the following occurs: a) write to atdctl5 (a new conversion sequence is started) b) if affc=0 and read of atdstat1 followed by read of result register atddrx c) if affc=1 and read of result register atddrx 0 conversion number x not completed 1 conversion number x has completed, result ready in atddrx chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 239 7.3.2.12 atd input enable register 0 (atddien0) read: anytime write: anytime 7.3.2.13 atd input enable register 1 (atddien1) read: anytime write: anytime module base + 0x000c 76543210 r ien15 ien14 ien13 ien12 ien11 ien10 ien9 ien8 w reset 0 0 0 00000 figure 7-14. input enable register 0 (atddien0) table 7-22. atddien0 field descriptions field description 7? ien[15:0] atd digital input enable on channel x (x = 15, 14, 13, 12, 11, 10, 9, 8) ?this bit controls the digital input buffer from the analog input pin (anx) to ptadx data register. 0 disable digital input buffer to ptadx 1 enable digital input buffer to ptadx. note: setting this bit will enable the corresponding digital input buffer continuously. if this bit is set while simultaneously using it as an analog port, there is potentially increased power consumption because the digital input buffer maybe in the linear region. module base + 0x000d 76543210 r ien7 ien6 ien5 ien4 ien3 ien2 ien1 ien0 w reset 0 0 0 00000 figure 7-15. input enable register 1 (atddien1) table 7-23. atddien1 field descriptions field description 7? ien[7:0] atd digital input enable on channel x (x = 7, 6, 5, 4, 3, 2, 1, 0) this bit controls the digital input buffer from the analog input pin (anx) to ptadx data register. 0 disable digital input buffer to ptadx 1 enable digital input buffer to ptadx. note: setting this bit will enable the corresponding digital input buffer continuously. if this bit is set while simultaneously using it as an analog port, there is potentially increased power consumption because the digital input buffer maybe in the linear region. chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 240 freescale semiconductor 7.3.2.14 port data register 0 (portad0) the data port associated with the atd is input-only. the port pins are shared with the analog a/d inputs an15-8. read: anytime write: anytime, no effect the a/d input channels may be used for general-purpose digital input. module base + 0x000e 76543210 r ptad15 ptad14 ptad13 ptad12 ptad11 ptad10 ptad9 ptad8 w reset 1 1 1 11111 pin function an 15 an14 an13 an12 an11 an10 an9 an8 = unimplemented or reserved figure 7-16. port data register 0 (portad0) table 7-24. portad0 field descriptions field description 7? ptad[15:0] a/d channel x (anx) digital input (x = 15, 14, 13, 12, 11, 10, 9, 8) if the digital input buffer on the anx pin is enabled (ienx = 1) or channel x is enabled as external trigger (etrige = 1, etrich[3-0] = x, etrigsel = 0) read returns the logic level on anx pin (signal potentials not meeting vil or vih speci?ations will have an indeterminate value)). if the digital input buffers are disabled (ienx = 0) and channel x is not enabled as external trigger, read returns a ?? reset sets all portad0 bits to ?? chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 241 7.3.2.15 port data register 1 (portad1) the data port associated with the atd is input-only. the port pins are shared with the analog a/d inputs an7-0. read: anytime write: anytime, no effect the a/d input channels may be used for general purpose digital input. 7.3.2.16 atd conversion result registers (atddrx) the a/d conversion results are stored in 16 read-only result registers. the result data is formatted in the result registers bases on two criteria. first there is left and right justi?ation; this selection is made using the djm control bit in atdctl5. second there is signed and unsigned data; this selection is made using the dsgn control bit in atdctl5. signed data is stored in 2 s complement format and only exists in left justi?d format. signed data selected for right justi?d format is ignored. read: anytime write: anytime in special mode, unimplemented in normal modes module base + 0x000f 76543210 r ptad7 ptad6 ptad5 ptad4 ptad3 ptad2 ptad1 ptad0 w reset 1 1 1 11111 pin function an 7 an6 an5 an4 an3 an2 an1 an0 = unimplemented or reserved figure 7-17. port data register 1 (portad1) table 7-25. portad1 field descriptions field description 7? ptad[7:0] a/d channel x (anx) digital input (x = 7, 6, 5, 4, 3, 2, 1, 0) if the digital input buffer on the anx pin is enabled (ienx = 1) or channel x is enabled as external trigger (etrige = 1, etrich[3-0] = x, etrigsel = 0) read returns the logic level on anx pin (signal potentials not meeting vil or vih speci?ations will have an indeterminate value)). if the digital input buffers are disabled (ienx = 0) and channel x is not enabled as external trigger, read returns a ?? reset sets all portad1 bits to ?? chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 242 freescale semiconductor 7.3.2.16.1 left justi?d result data 7.3.2.16.2 right justi?d result data module base + 0x0010 = atddr0h, 0x0012 = atddr1h, 0x0014 = atddr2h, 0x0016 = atddr3h 0x0018 = atddr4h, 0x001a = atddr5h, 0x001c = atddr6h, 0x001e = atddr7h 0x0020 = atddr8h, 0x0022 = atddr9h, 0x0024 = atddr10h, 0x0026 = atddr11h 0x0028 = atddr12h, 0x002a = atddr13h, 0x002c = atddr14h, 0x002e = atddr15h 76543210 r w bit 9 msb bit 7 msb bit 8 bit 6 bit 7 bit 5 bit 6 bit 4 bit 5 bit 3 bit 4 bit 2 bit 3 bit 1 bit 2 bit 0 10-bit data 8-bit data reset 0 0 0 0 0 0 0 0 figure 7-18. left justi?d, atd conversion result register, high byte (atddrxh) module base + 0x0011 = atddr0l, 0x0013 = atddr1l, 0x0015 = atddr2l, 0x0017 = atddr3l 0x0019 = atddr4l, 0x001b = atddr5l, 0x001d = atddr6l, 0x001f = atddr7l 0x0021 = atddr8l, 0x0023 = atddr9l, 0x0025 = atddr10l, 0x0027 = atddr11l 0x0029 = atddr12l, 0x002b = atddr13l, 0x002d = atddr14l, 0x002f = atddr15l 76543210 r w bit 1 u bit 0 u 0 0 0 0 0 0 0 0 0 0 0 0 10-bit data 8-bit data reset 0 0 0 0 0 0 0 0 figure 7-19. left justi?d, atd conversion result register, low byte (atddrxl) module base + 0x0010 = atddr0h, 0x0012 = atddr1h, 0x0014 = atddr2h, 0x0016 = atddr3h 0x0018 = atddr4h, 0x001a = atddr5h, 0x001c = atddr6h, 0x001e = atddr7h 0x0020 = atddr8h, 0x0022 = atddr9h, 0x0024 = atddr10h, 0x0026 = atddr11h 0x0028 = atddr12h, 0x002a = atddr13h, 0x002c = atddr14h, 0x002e = atddr15h 76543210 r w 0 0 0 0 0 0 0 0 0 0 0 0 bit 9 msb 0 bit 8 0 10-bit data 8-bit data reset 0 0 0 0 0 0 0 0 figure 7-20. right justi?d, atd conversion result register, high byte (atddrxh) module base + 0x0011 = atddr0l, 0x0013 = atddr1l, 0x0015 = atddr2l, 0x0017 = atddr3l 0x0019 = atddr4l, 0x001b = atddr5l, 0x001d = atddr6l, 0x001f = atddr7l 0x0021 = atddr8l, 0x0023 = atddr9l, 0x0025 = atddr10l, 0x0027 = atddr11l 0x0029 = atddr12l, 0x002b = atddr13l, 0x002d = atddr14l, 0x002f = atddr15l 76543210 r w bit 7 bit 7 msb bit 6 bit 6 bit 5 bit 5 bit 4 bit 4 bit 3 bit 3 bit 2 bit 2 bit 1 bit 1 bit 0 bit 0 10-bit data 8-bit data reset 0 0 0 0 0 0 0 0 figure 7-21. right justi?d, atd conversion result register, low byte (atddrxl) chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 243 7.4 functional description the atd is structured in an analog and a digital sub-block. 7.4.1 analog sub-block the analog sub-block contains all analog electronics required to perform a single conversion. separate power supplies vdda and vssa allow to isolate noise of other mcu circuitry from the analog sub-block. 7.4.1.1 sample and hold machine the sample and hold (s/h) machine accepts analog signals from the external world and stores them as capacitor charge on a storage node. the sample process uses a two stage approach. during the ?st stage, the sample ampli?r is used to quickly charge the storage node.the second stage connects the input directly to the storage node to complete the sample for high accuracy. when not sampling, the sample and hold machine disables its own clocks. the analog electronics still draw their quiescent current. the power down (adpu) bit must be set to disable both the digital clocks and the analog power consumption. the input analog signals are unipolar and must fall within the potential range of vssa to vdda. 7.4.1.2 analog input multiplexer the analog input multiplexer connects one of the 16 external analog input channels to the sample and hold machine. 7.4.1.3 sample buffer ampli?r the sample ampli?r is used to buffer the input analog signal so that the storage node can be quickly charged to the sample potential. 7.4.1.4 analog-to-digital (a/d) machine the a/d machine performs analog to digital conversions. the resolution is program selectable at either 8 or 10 bits. the a/d machine uses a successive approximation architecture. it functions by comparing the stored analog sample potential with a series of digitally generated analog potentials. by following a binary search algorithm, the a/d machine locates the approximating potential that is nearest to the sampled potential. when not converting the a/d machine disables its own clocks. the analog electronics still draws quiescent current. the power down (adpu) bit must be set to disable both the digital clocks and the analog power consumption. only analog input signals within the potential range of v rl to v rh (a/d reference potentials) will result in a non-railed digital output codes. chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 244 freescale semiconductor 7.4.2 digital sub-block this subsection explains some of the digital features in more detail. see register descriptions for all details. 7.4.2.1 external trigger input the external trigger feature allows the user to synchronize atd conversions to the external environment events rather than relying on software to signal the atd module when atd conversions are to take place. the external trigger signal (out of reset atd channel 15, con?urable in atdctl1) is programmable to be edge or level sensitive with polarity control. table 7-26 gives a brief description of the different combinations of control bits and their affect on the external trigger function. during a conversion, if additional active edges are detected the overrun error ?g etorf is set. in either level or edge triggered modes, the ?st conversion begins when the trigger is received. in both cases, the maximum latency time is one bus clock cycle plus any skew or delay introduced by the trigger circuitry. once etrige is enabled, conversions cannot be started by a write to atdctl5, but rather must be triggered externally. if the level mode is active and the external trigger both de-asserts and re-asserts itself during a conversion sequence, this does not constitute an overrun. therefore, the ?g is not set. if the trigger is left asserted in level mode while a sequence is completing, another sequence will be triggered immediately. 7.4.2.2 general-purpose digital input port operation the input channel pins can be multiplexed between analog and digital data. as analog inputs, they are multiplexed and sampled to supply signals to the a/d converter. as digital inputs, they supply external input data that can be accessed through the digital port registers (portad0 & portad1) (input-only). table 7-26. external trigger control bits etrigle etrigp etrige scan description x x 0 0 ignores external trigger. performs one conversion sequence and stops. x x 0 1 ignores external trigger. performs continuous conversion sequences. 0 0 1 x falling edge triggered. performs one conversion sequence per trigger. 0 1 1 x rising edge triggered. performs one conversion sequence per trigger. 1 0 1 x trigger active low. performs continuous conversions while trigger is active. 1 1 1 x trigger active high. performs continuous conversions while trigger is active. chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 245 the analog/digital multiplex operation is performed in the input pads. the input pad is always connected to the analog inputs of the atd. the input pad signal is buffered to the digital port registers. this buffer can be turned on or off with the atddien0 & atddien1 register. this is important so that the buffer does not draw excess current when analog potentials are presented at its input. 7.4.2.3 low-power modes the atd can be con?ured for lower mcu power consumption in three different ways: stop mode: this halts a/d conversion. exit from stop mode will resume a/d conversion, but due to the recovery time the result of this conversion should be ignored. wait mode with awai = 1: this halts a/d conversion. exit from wait mode will resume a/d conversion, but due to the recovery time the result of this conversion should be ignored. writing adpu = 0 (note that all atd registers remain accessible.): this aborts any a/d conversion in progress. note the reset value for the adpu bit is zero. therefore, when this module is reset, it is reset into the power down state. 7.5 resets at reset the atd is in a power down state. the reset state of each individual bit is listed within the register description section (see section 7.3, ?emory map and register de?ition ) which details the registers and their bit-?ld. 7.6 interrupts the interrupt requested by the atd is listed in table 7-27 . refer to mcu speci?ation for related vector address and priority. see section 7.3, ?emory map and register de?ition for further details. table 7-27. atd interrupt vectors interrupt source ccr mask local enable sequence complete interrupt i bit ascie in atdctl2 chapter 7 analog-to-digital converter (atd10b16cv1) mc9s12kg128 data sheet, rev. 1.15 246 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 247 chapter 8 inter-integrated circuit (iicv2) 8.1 introduction the inter-ic bus (iic) is a two-wire, bidirectional serial bus that provides a simple, ef?ient method of data exchange between devices. being a two-wire device, the iic bus minimizes the need for large numbers of connections between devices, and eliminates the need for an address decoder. this bus is suitable for applications requiring occasional communications over a short distance between a number of devices. it also provides ?xibility, allowing additional devices to be connected to the bus for further expansion and system development. the interface is designed to operate up to 100 kbps with maximum bus loading and timing. the device is capable of operating at higher baud rates, up to a maximum of clock/20, with reduced bus loading. the maximum communication length and the number of devices that can be connected are limited by a maximum bus capacitance of 400 pf. 8.1.1 features the iic module has the following key features: compatible with i2c bus standard multi-master operation software programmable for one of 256 different serial clock frequencies software selectable acknowledge bit interrupt driven byte-by-byte data transfer arbitration lost interrupt with automatic mode switching from master to slave calling address identi?ation interrupt start and stop signal generation/detection repeated start signal generation acknowledge bit generation/detection bus busy detection chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 248 freescale semiconductor 8.1.2 modes of operation the iic functions the same in normal, special, and emulation modes. it has two low power modes: wait and stop modes. 8.1.3 block diagram the block diagram of the iic module is shown in figure 8-1 . figure 8-1. iic block diagram in/out data shift register address compare sda interrupt clock control start stop arbitration control scl bus_clock iic registers chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 249 8.2 external signal description the iic module has two external pins. 8.2.1 iic_scl ?serial clock line pin this is the bidirectional serial clock line (scl) of the module, compatible to the iic bus speci?ation. 8.2.2 iic_sda ?serial data line pin this is the bidirectional serial data line (sda) of the module, compatible to the iic bus speci?ation. 8.3 memory map and register de?ition this section provides a detailed description of all memory and registers for the iic module. 8.3.1 module memory map the memory map for the iic module is given below in table 8-1 . the address listed for each register is the address offset.the total address for each register is the sum of the base address for the iic module and the address offset for each register. chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 250 freescale semiconductor 8.3.2 register descriptions this section consists of register descriptions in address order. each description includes a standard register diagram with an associated ?ure number. details of register bit and ?ld function follow the register diagrams, in bit order. 8.3.2.1 iic address register (ibad) read and write anytime this register contains the address the iic bus will respond to when addressed as a slave; note that it is not the address sent on the bus during the address transfer. register name bit 7 654321 bit 0 ibad r adr7 adr6 adr5 adr4 adr3 adr2 adr1 0 w ibfd r ibc7 ibc6 ibc5 ibc4 ibc3 ibc2 ibc1 ibc0 w ibcr r iben ibie ms/ sl tx/ rx txak 00 ibswai w rsta ibsr r tcf iaas ibb ibal 0srw ibif rxak w ibdr r d7 d6 d5 d4 d3 d2 d1 d0 w = unimplemented or reserved table 8-1. iic register summary 76543210 r adr7 adr6 adr5 adr4 adr3 adr2 adr1 0 w reset 0 0 0 00000 = unimplemented or reserved figure 8-2. iic bus address register (ibad) table 8-2. ibad field descriptions field description 7:1 adr[7:1] slave address bit 1 to bit 7 contain the speci? slave address to be used by the iic bus module.the default mode of iic bus is slave mode for an address match on the bus. 0 reserved reserved ?bit 0 of the ibad is reserved for future compatibility. this bit will always read 0. chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 251 8.3.2.2 iic frequency divider register (ibfd) read and write anytime 76543210 r ibc7 ibc6 ibc5 ibc4 ibc3 ibc2 ibc1 ibc0 w reset 0 0 0 00000 = unimplemented or reserved figure 8-3. iic bus frequency divider register (ibfd) table 8-3. ibfd field descriptions field description 7:0 ibc[7:0] i bus clock rate 7:0 ?this ?ld is used to prescale the clock for bit rate selection. the bit clock generator is implemented as a prescale divider ibc7:6, prescaled shift register ibc5:3 select the prescaler divider and ibc2-0 select the shift register tap point. the ibc bits are decoded to give the tap and prescale values as shown in table 8-4 . table 8-4. i-bus tap and prescale values ibc2-0 (bin) scl tap (clocks) sda tap (clocks) 000 5 1 001 6 1 010 7 2 011 8 2 100 9 3 101 10 3 110 12 4 111 15 4 ibc5-3 (bin) scl2start (clocks) scl2stop (clocks) scl2tap (clocks) tap2tap (clocks) 0002741 0012742 0102964 0116968 100 14 17 14 16 101 30 33 30 32 110 62 65 62 64 111 126 129 126 128 chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 252 freescale semiconductor the number of clocks from the falling edge of scl to the ?st tap (tap[1]) is de?ed by the values shown in the scl2tap column of table 8-4 , all subsequent tap points are separated by 2 ibc5-3 as shown in the tap2tap column in table 8-4 . the scl tap is used to generated the scl period and the sda tap is used to determine the delay from the falling edge of scl to sda changing, the sda hold time. ibc7? de?es the multiplier factor mul. the values of mul are shown in the table 8-5 . figure 8-4. scl divider and sda hold the equation used to generate the divider values from the ibfd bits is: scl divider = mul x {2 x (scl2tap + [(scl_tap -1) x tap2tap] + 2)} table 8-5. multiplier factor ibc7-6 mul 00 01 01 02 10 04 11 reserved scl divider sda hold scl sda sda scl start condition stop condition scl hold(start) scl hold(stop) chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 253 the sda hold delay is equal to the cpu clock period multiplied by the sda hold value shown in table 8-6 . the equation used to generate the sda hold value from the ibfd bits is: sda hold = mul x {scl2tap + [(sda_tap - 1) x tap2tap] + 3} the equation for scl hold values to generate the start and stop conditions from the ibfd bits is: scl hold(start) = mul x [scl2start + (scl_tap - 1) x tap2tap] scl hold(stop) = mul x [scl2stop + (scl_tap - 1) x tap2tap] table 8-6. iic divider and hold values (sheet 1 of 5) ibc[7:0] (hex) scl divider (clocks) sda hold (clocks) scl hold (start) scl hold (stop) mul=1 00 20 7 6 11 01 22 7 7 12 02 24 8 8 13 03 26 8 9 14 04 28 9 10 15 05 30 9 11 16 06 34 10 13 18 07 40 10 16 21 08 28 7 10 15 09 32 7 12 17 0a 36 9 14 19 0b 40 9 16 21 0c 44 11 18 23 0d 48 11 20 25 0e 56 13 24 29 0f 68 13 30 35 10 48 9 18 25 11 56 9 22 29 12 64 13 26 33 13 72 13 30 37 14 80 17 34 41 15 88 17 38 45 16 104 21 46 53 17 128 21 58 65 18 80 9 38 41 19 96 9 46 49 1a 112 17 54 57 1b 128 17 62 65 1c 144 25 70 73 1d 160 25 78 81 1e 192 33 94 97 1f 240 33 118 121 20 160 17 78 81 21 192 17 94 97 22 224 33 110 113 chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 254 freescale semiconductor 23 256 33 126 129 24 288 49 142 145 25 320 49 158 161 26 384 65 190 193 27 480 65 238 241 28 320 33 158 161 29 384 33 190 193 2a 448 65 222 225 2b 512 65 254 257 2c 576 97 286 289 2d 640 97 318 321 2e 768 129 382 385 2f 960 129 478 481 30 640 65 318 321 31 768 65 382 385 32 896 129 446 449 33 1024 129 510 513 34 1152 193 574 577 35 1280 193 638 641 36 1536 257 766 769 37 1920 257 958 961 38 1280 129 638 641 39 1536 129 766 769 3a 1792 257 894 897 3b 2048 257 1022 1025 3c 2304 385 1150 1153 3d 2560 385 1278 1281 3e 3072 513 1534 1537 3f 3840 513 1918 1921 mul=2 40 40 14 12 22 41 44 14 14 24 42 48 16 16 26 43 52 16 18 28 44 56 18 20 30 45 60 18 22 32 46 68 20 26 36 47 80 20 32 42 48 56 14 20 30 49 64 14 24 34 4a 72 18 28 38 4b 80 18 32 42 4c 88 22 36 46 4d 96 22 40 50 4e 112 26 48 58 table 8-6. iic divider and hold values (sheet 2 of 5) ibc[7:0] (hex) scl divider (clocks) sda hold (clocks) scl hold (start) scl hold (stop) chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 255 4f 136 26 60 70 50 96 18 36 50 51 112 18 44 58 52 128 26 52 66 53 144 26 60 74 54 160 34 68 82 55 176 34 76 90 56 208 42 92 106 57 256 42 116 130 58 160 18 76 82 59 192 18 92 98 5a 224 34 108 114 5b 256 34 124 130 5c 288 50 140 146 5d 320 50 156 162 5e 384 66 188 194 5f 480 66 236 242 60 320 34 156 162 61 384 34 188 194 62 448 66 220 226 63 512 66 252 258 64 576 98 284 290 65 640 98 316 322 66 768 130 380 386 67 960 130 476 482 68 640 66 316 322 69 768 66 380 386 6a 896 130 444 450 6b 1024 130 508 514 6c 1152 194 572 578 6d 1280 194 636 642 6e 1536 258 764 770 6f 1920 258 956 962 70 1280 130 636 642 71 1536 130 764 770 72 1792 258 892 898 73 2048 258 1020 1026 74 2304 386 1148 1154 75 2560 386 1276 1282 76 3072 514 1532 1538 77 3840 514 1916 1922 78 2560 258 1276 1282 79 3072 258 1532 1538 7a 3584 514 1788 1794 7b 4096 514 2044 2050 table 8-6. iic divider and hold values (sheet 3 of 5) ibc[7:0] (hex) scl divider (clocks) sda hold (clocks) scl hold (start) scl hold (stop) chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 256 freescale semiconductor 7c 4608 770 2300 2306 7d 5120 770 2556 2562 7e 6144 1026 3068 3074 7f 7680 1026 3836 3842 mul=4 80 80 28 24 44 81 88 28 28 48 82 96 32 32 52 83 104 32 36 56 84 112 36 40 60 85 120 36 44 64 86 136 40 52 72 87 160 40 64 84 88 112 28 40 60 89 128 28 48 68 8a 144 36 56 76 8b 160 36 64 84 8c 176 44 72 92 8d 192 44 80 100 8e 224 52 96 116 8f 272 52 120 140 90 192 36 72 100 91 224 36 88 116 92 256 52 104 132 93 288 52 120 148 94 320 68 136 164 95 352 68 152 180 96 416 84 184 212 97 512 84 232 260 98 320 36 152 164 99 384 36 184 196 9a 448 68 216 228 9b 512 68 248 260 9c 576 100 280 292 9d 640 100 312 324 9e 768 132 376 388 9f 960 132 472 484 a0 640 68 312 324 a1 768 68 376 388 a2 896 132 440 452 a3 1024 132 504 516 a4 1152 196 568 580 a5 1280 196 632 644 a6 1536 260 760 772 a7 1920 260 952 964 table 8-6. iic divider and hold values (sheet 4 of 5) ibc[7:0] (hex) scl divider (clocks) sda hold (clocks) scl hold (start) scl hold (stop) chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 257 8.3.2.3 iic control register (ibcr) read and write anytime a8 1280 132 632 644 a9 1536 132 760 772 aa 1792 260 888 900 ab 2048 260 1016 1028 ac 2304 388 1144 1156 ad 2560 388 1272 1284 ae 3072 516 1528 1540 af 3840 516 1912 1924 b0 2560 260 1272 1284 b1 3072 260 1528 1540 b2 3584 516 1784 1796 b3 4096 516 2040 2052 b4 4608 772 2296 2308 b5 5120 772 2552 2564 b6 6144 1028 3064 3076 b7 7680 1028 3832 3844 b8 5120 516 2552 2564 b9 6144 516 3064 3076 ba 7168 1028 3576 3588 bb 8192 1028 4088 4100 bc 9216 1540 4600 4612 bd 10240 1540 5112 5124 be 12288 2052 6136 6148 bf 15360 2052 7672 7684 76543210 r iben ibie ms/sl tx/rx txak 00 ibswai w rsta reset 0 0 0 00000 = unimplemented or reserved figure 8-5. iic bus control register (ibcr) table 8-6. iic divider and hold values (sheet 5 of 5) ibc[7:0] (hex) scl divider (clocks) sda hold (clocks) scl hold (start) scl hold (stop) chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 258 freescale semiconductor wait mode is entered via execution of a cpu wai instruction. in the event that the ibswai bit is set, all clocks internal to the iic will be stopped and any transmission currently in progress will halt.if the cpu were woken up by a source other than the iic module, then clocks would restart and the iic would resume table 8-7. ibcr field descriptions field description 7 iben i-bus enable ?this bit controls the software reset of the entire iic bus module. 0 the module is reset and disabled. this is the power-on reset situation. when low the interface is held in reset but registers can be accessed 1 the iic bus module is enabled.this bit must be set before any other ibcr bits have any effect if the iic bus module is enabled in the middle of a byte transfer the interface behaves as follows: slave mode ignores the current transfer on the bus and starts operating whenever a subsequent start condition is detected. master mode will not be aware that the bus is busy, hence if a start cycle is initiated then the current bus cycle may become corrupt. this would ultimately result in either the current bus master or the iic bus module losing arbitration, after which bus operation would return to normal. 6 ibie i-bus interrupt enable 0 interrupts from the iic bus module are disabled. note that this does not clear any currently pending interrupt condition 1 interrupts from the iic bus module are enabled. an iic bus interrupt occurs provided the ibif bit in the status register is also set. 5 ms/sl master/slave mode select bit upon reset, this bit is cleared. when this bit is changed from 0 to 1, a start signal is generated on the bus, and the master mode is selected. when this bit is changed from 1 to 0, a stop signal is generated and the operation mode changes from master to slave.a stop signal should only be generated if the ibif ?g is set. ms/ sl is cleared without generating a stop signal when the master loses arbitration. 0 slave mode 1 master mode 4 tx/rx transmit/receive mode select bit ?this bit selects the direction of master and slave transfers. when addressed as a slave this bit should be set by software according to the srw bit in the status register. in master mode this bit should be set according to the type of transfer required. therefore, for address cycles, this bit will always be high. 0 receive 1 transmit 3 txak transmit acknowledge enable this bit speci?s the value driven onto sda during data acknowledge cycles for both master and slave receivers. the iic module will always acknowledge address matches, provided it is enabled, regardless of the value of txak. note that values written to this bit are only used when the iic bus is a receiver, not a transmitter. 0 an acknowledge signal will be sent out to the bus at the 9th clock bit after receiving one byte data 1 no acknowledge signal response is sent (i.e., acknowledge bit = 1) 2 rsta repeat start ?writing a 1 to this bit will generate a repeated start condition on the bus, provided it is the current bus master. this bit will always be read as a low. attempting a repeated start at the wrong time, if the bus is owned by another master, will result in loss of arbitration. 1 generate repeat start cycle 1 reserved reserved ?bit 1 of the ibcr is reserved for future compatibility. this bit will always read 0. 0 ibswai i bus interface stop in wait mode 0 iic bus module clock operates normally 1 halt iic bus module clock generation in wait mode chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 259 from where was during the previous transmission. it is not possible for the iic to wake up the cpu when its internal clocks are stopped. if it were the case that the ibswai bit was cleared when the wai instruction was executed, the iic internal clocks and interface would remain alive, continuing the operation which was currently underway. it is also possible to con?ure the iic such that it will wake up the cpu via an interrupt at the conclusion of the current operation. see the discussion on the ibif and ibie bits in the ibsr and ibcr, respectively. 8.3.2.4 iic status register (ibsr) this status register is read-only with exception of bit 1 (ibif) and bit 4 (ibal), which are software clearable. 76543210 r tcf iaas ibb ibal 0srw ibif rxak w reset 1 0 0 00000 = unimplemented or reserved figure 8-6. iic bus status register (ibsr) table 8-8. ibsr field descriptions field description 7 tcf data transferring bit ?while one byte of data is being transferred, this bit is cleared. it is set by the falling edge of the 9th clock of a byte transfer. note that this bit is only valid during or immediately following a transfer to the iic module or from the iic module. 0 transfer in progress 1 transfer complete 6 iaas addressed as a slave bit when its own speci? address (i-bus address register) is matched with the calling address, this bit is set.the cpu is interrupted provided the ibie is set.then the cpu needs to check the srw bit and set its tx/ rx mode accordingly.writing to the i-bus control register clears this bit. 0 not addressed 1 addressed as a slave 5 ibb bus busy bit 0 this bit indicates the status of the bus. when a start signal is detected, the ibb is set. if a stop signal is detected, ibb is cleared and the bus enters idle state. 1 bus is busy 4 ibal arbitration lost ?the arbitration lost bit (ibal) is set by hardware when the arbitration procedure is lost. arbitration is lost in the following circumstances: 1. sda sampled low when the master drives a high during an address or data transmit cycle. 2. sda sampled low when the master drives a high during the acknowledge bit of a data receive cycle. 3. a start cycle is attempted when the bus is busy. 4. a repeated start cycle is requested in slave mode. 5. a stop condition is detected when the master did not request it. this bit must be cleared by software, by writing a one to it. a write of 0 has no effect on this bit. 3 reserved reserved ?bit 3 of ibsr is reserved for future use. a read operation on this bit will return 0. chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 260 freescale semiconductor 8.3.2.5 iic data i/o register (ibdr) in master transmit mode, when data is written to the ibdr a data transfer is initiated. the most signi?ant bit is sent ?st. in master receive mode, reading this register initiates next byte data receiving. in slave mode, the same functions are available after an address match has occurred.note that the tx/rx bit in the ibcr must correctly re?ct the desired direction of transfer in master and slave modes for the transmission to begin. for instance, if the iic is con?ured for master transmit but a master receive is desired, then reading the ibdr will not initiate the receive. reading the ibdr will return the last byte received while the iic is con?ured in either master receive or slave receive modes. the ibdr does not re?ct every byte that is transmitted on the iic bus, nor can software verify that a byte has been written to the ibdr correctly by reading it back. in master transmit mode, the ?st byte of data written to ibdr following assertion of ms/ sl is used for the address transfer and should com.prise of the calling address (in position d7:d1) concatenated with the required r/ w bit (in position d0). 2 srw slave read/write when iaas is set this bit indicates the value of the r/w command bit of the calling address sent from the master this bit is only valid when the i-bus is in slave mode, a complete address transfer has occurred with an address match and no other transfers have been initiated. checking this bit, the cpu can select slave transmit/receive mode according to the command of the master. 0 slave receive, master writing to slave 1 slave transmit, master reading from slave 1 ibif i-bus interrupt ?the ibif bit is set when one of the following conditions occurs: ?arbitration lost (ibal bit set) ?byte transfer complete (tcf bit set) ?addressed as slave (iaas bit set) it will cause a processor interrupt request if the ibie bit is set. this bit must be cleared by software, writing a one to it. a write of 0 has no effect on this bit. 0 rxak received acknowledge ?the value of sda during the acknowledge bit of a bus cycle. if the received acknowledge bit (rxak) is low, it indicates an acknowledge signal has been received after the completion of 8 bits data transmission on the bus. if rxak is high, it means no acknowledge signal is detected at the 9th clock. 0 acknowledge received 1 no acknowledge received 76543210 r d7 d6 d5 d4 d3 d2 d1 d0 w reset 0 0 0 00000 figure 8-7. iic bus data i/o register (ibdr) table 8-8. ibsr field descriptions (continued) field description chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 261 8.4 functional description this section provides a complete functional description of the iic. 8.4.1 i-bus protocol the iic bus system uses a serial data line (sda) and a serial clock line (scl) for data transfer. all devices connected to it must have open drain or open collector outputs. logic and function is exercised on both lines with external pull-up resistors. the value of these resistors is system dependent. normally, a standard communication is composed of four parts: start signal, slave address transmission, data transfer and stop signal. they are described brie? in the following sections and illustrated in figure 8-8 . figure 8-8. iic-bus transmission signals 8.4.1.1 start signal when the bus is free, i.e. no master device is engaging the bus (both scl and sda lines are at logical high), a master may initiate communication by sending a start signal.as shown in figure 8-8 , a start signal is de?ed as a high-to-low transition of sda while scl is high. this signal denotes the beginning of a new data transfer (each data transfer may contain several bytes of data) and brings all slaves out of their idle states. scl sda start signal ack bit 12345678 msb lsb 12345678 msb lsb stop signal no scl sda 1234567 8 msb lsb 1 2 5 678 msb lsb repeated 34 99 ad7 ad6 ad5 ad4 ad3 ad2 ad1 r/w xxx d7 d6 d5 d4 d3 d2 d1 d0 calling address read/ data byte ad7 ad6 ad5 ad4 ad3 ad2 ad1 r/w ad7 ad6 ad5 ad4 ad3 ad2 ad1 r/w new calling address 99 xx ack bit write start signal start signal ack bit calling address read/ write stop signal no ack bit read/ write chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 262 freescale semiconductor figure 8-9. start and stop conditions 8.4.1.2 slave address transmission the ?st byte of data transfer immediately after the start signal is the slave address transmitted by the master. this is a seven-bit calling address followed by a r/w bit. the r/w bit tells the slave the desired direction of data transfer. 1 = read transfer, the slave transmits data to the master. 0 = write transfer, the master transmits data to the slave. only the slave with a calling address that matches the one transmitted by the master will respond by sending back an acknowledge bit. this is done by pulling the sda low at the 9th clock (see figure 8-8 ). no two slaves in the system may have the same address. if the iic bus is master, it must not transmit an address that is equal to its own slave address. the iic bus cannot be master and slave at the same time.however, if arbitration is lost during an address cycle the iic bus will revert to slave mode and operate correctly even if it is being addressed by another master. 8.4.1.3 data transfer as soon as successful slave addressing is achieved, the data transfer can proceed byte-by-byte in a direction speci?d by the r/w bit sent by the calling master all transfers that come after an address cycle are referred to as data transfers, even if they carry sub-address information for the slave device. each data byte is 8 bits long. data may be changed only while scl is low and must be held stable while scl is high as shown in figure 8-8 . there is one clock pulse on scl for each data bit, the msb being transferred ?st. each data byte has to be followed by an acknowledge bit, which is signalled from the receiving device by pulling the sda low at the ninth clock. so one complete data byte transfer needs nine clock pulses. if the slave receiver does not acknowledge the master, the sda line must be left high by the slave. the master can then generate a stop signal to abort the data transfer or a start signal (repeated start) to commence a new calling. sda scl start condition stop condition chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 263 if the master receiver does not acknowledge the slave transmitter after a byte transmission, it means 'end of data' to the slave, so the slave releases the sda line for the master to generate stop or start signal. 8.4.1.4 stop signal the master can terminate the communication by generating a stop signal to free the bus. however, the master may generate a start signal followed by a calling command without generating a stop signal ?st. this is called repeated start. a stop signal is de?ed as a low-to-high transition of sda while scl at logical 1 (see figure 8-8 ). the master can generate a stop even if the slave has generated an acknowledge at which point the slave must release the bus. 8.4.1.5 repeated start signal as shown in figure 8-8 , a repeated start signal is a start signal generated without ?st generating a stop signal to terminate the communication. this is used by the master to communicate with another slave or with the same slave in different mode (transmit/receive mode) without releasing the bus. 8.4.1.6 arbitration procedure the inter-ic bus is a true multi-master bus that allows more than one master to be connected on it. if two or more masters try to control the bus at the same time, a clock synchronization procedure determines the bus clock, for which the low period is equal to the longest clock low period and the high is equal to the shortest one among the masters. the relative priority of the contending masters is determined by a data arbitration procedure, a bus master loses arbitration if it transmits logic 1 while another master transmits logic 0. the losing masters immediately switch over to slave receive mode and stop driving sda output. in this case the transition from master to slave mode does not generate a stop condition. meanwhile, a status bit is set by hardware to indicate loss of arbitration. 8.4.1.7 clock synchronization because wire-and logic is performed on scl line, a high-to-low transition on scl line affects all the devices connected on the bus. the devices start counting their low period and as soon as a device's clock has gone low, it holds the scl line low until the clock high state is reached.however, the change of low to high in this device clock may not change the state of the scl line if another device clock is within its low period. therefore, synchronized clock scl is held low by the device with the longest low period. devices with shorter low periods enter a high wait state during this time (see figure 8-9 ). when all devices concerned have counted off their low period, the synchronized clock scl line is released and pulled high. there is then no difference between the device clocks and the state of the scl line and all the devices start counting their high periods.the ?st device to complete its high period pulls the scl line low again. chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 264 freescale semiconductor figure 8-10. iic-bus clock synchronization 8.4.1.8 handshaking the clock synchronization mechanism can be used as a handshake in data transfer. slave devices may hold the scl low after completion of one byte transfer (9 bits). in such case, it halts the bus clock and forces the master clock into wait states until the slave releases the scl line. 8.4.1.9 clock stretching the clock synchronization mechanism can be used by slaves to slow down the bit rate of a transfer. after the master has driven scl low the slave can drive scl low for the required period and then release it.if the slave scl low period is greater than the master scl low period then the resulting scl bus signal low period is stretched. 8.4.2 operation in run mode this is the basic mode of operation. 8.4.3 operation in wait mode iic operation in wait mode can be con?ured. depending on the state of internal bits, the iic can operate normally when the cpu is in wait mode or the iic clock generation can be turned off and the iic module enters a power conservation state during wait mode. in the later case, any transmission or reception in progress stops at wait mode entry. 8.4.4 operation in stop mode the iic is inactive in stop mode for reduced power consumption. the stop instruction does not affect iic register states. scl1 scl2 scl internal counter reset wait start counting high period chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 265 8.5 resets the reset state of each individual bit is listed in section 8.3, ?emory map and register de?ition , which details the registers and their bit-?lds. 8.6 interrupts iic uses only one interrupt vector. table 8-9. interrupt summary internally there are three types of interrupts in iic. the interrupt service routine can determine the interrupt type by reading the status register. iic interrupt can be generated on 1. arbitration lost condition (ibal bit set) 2. byte transfer condition (tcf bit set) 3. address detect condition (iaas bit set) the iic interrupt is enabled by the ibie bit in the iic control register. it must be cleared by writing 0 to the ibf bit in the interrupt service routine. 8.7 initialization/application information 8.7.1 iic programming examples 8.7.1.1 initialization sequence reset will put the iic bus control register to its default status. before the interface can be used to transfer serial data, an initialization procedure must be carried out, as follows: 1. update the frequency divider register (ibfd) and select the required division ratio to obtain scl frequency from system clock. 2. update the iic bus address register (ibad) to de?e its slave address. 3. set the iben bit of the iic bus control register (ibcr) to enable the iic interface system. 4. modify the bits of the iic bus control register (ibcr) to select master/slave mode, transmit/receive mode and interrupt enable or not. interrupt offset vector priority source description iic interrupt ibal, tcf, iaas bits in ibsr register when either of ibal, tcf or iaas bits is set may cause an interrupt based on arbitration lost, transfer complete or address detect conditions chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 266 freescale semiconductor 8.7.1.2 generation of start after completion of the initialization procedure, serial data can be transmitted by selecting the 'master transmitter' mode. if the device is connected to a multi-master bus system, the state of the iic bus busy bit (ibb) must be tested to check whether the serial bus is free. if the bus is free (ibb=0), the start condition and the ?st byte (the slave address) can be sent. the data written to the data register comprises the slave calling address and the lsb set to indicate the direction of transfer required from the slave. the bus free time (i.e., the time between a stop condition and the following start condition) is built into the hardware that generates the start cycle. depending on the relative frequencies of the system clock and the scl period it may be necessary to wait until the iic is busy after writing the calling address to the ibdr before proceeding with the following instructions. this is illustrated in the following example. an example of a program which generates the start signal and transmits the ?st byte of data (slave address) is shown below: 8.7.1.3 post-transfer software response transmission or reception of a byte will set the data transferring bit (tcf) to 1, which indicates one byte communication is ?ished. the iic bus interrupt bit (ibif) is set also; an interrupt will be generated if the interrupt function is enabled during initialization by setting the ibie bit. software must clear the ibif bit in the interrupt routine ?st. the tcf bit will be cleared by reading from the iic bus data i/o register (ibdr) in receive mode or writing to ibdr in transmit mode. software may service the iic i/o in the main program by monitoring the ibif bit if the interrupt function is disabled. note that polling should monitor the ibif bit rather than the tcf bit because their operation is different when arbitration is lost. note that when an interrupt occurs at the end of the address cycle the master will always be in transmit mode, i.e. the address is transmitted. if master receive mode is required, indicated by r/w bit in ibdr, then the tx/rx bit should be toggled at this stage. during slave mode address cycles (iaas=1), the srw bit in the status register is read to determine the direction of the subsequent transfer and the tx/rx bit is programmed accordingly. for slave mode data cycles (iaas=0) the srw bit is not valid, the tx/rx bit in the control register should be read to determine the direction of the current transfer. the following is an example of a software response by a 'master transmitter' in the interrupt routine. chflag brset ibsr,#$20,* ;wait for ibb flag to clear txstart bset ibcr,#$30 ;set transmit and master mode;i.e. generate start condition movb calling,ibdr ;transmit the calling address, d0=r/w ibfree brclr ibsr,#$20,* ;wait for ibb flag to set isr bclr ibsr,#$02 ;clear the ibif flag brclr ibcr,#$20,slave ;branch if in slave mode brclr ibcr,#$10,receive ;branch if in receive mode brset ibsr,#$01,end ;if no ack, end of transmission transmit movb databuf,ibdr ;transmit next byte of data chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 267 8.7.1.4 generation of stop a data transfer ends with a stop signal generated by the 'master' device. a master transmitter can simply generate a stop signal after all the data has been transmitted. the following is an example showing how a stop condition is generated by a master transmitter. if a master receiver wants to terminate a data transfer, it must inform the slave transmitter by not acknowledging the last byte of data which can be done by setting the transmit acknowledge bit (txak) before reading the 2nd last byte of data. before reading the last byte of data, a stop signal must be generated ?st. the following is an example showing how a stop signal is generated by a master receiver. 8.7.1.5 generation of repeated start at the end of data transfer, if the master continues to want to communicate on the bus, it can generate another start signal followed by another slave address without ?st generating a stop signal. a program example is as shown. 8.7.1.6 slave mode in the slave interrupt service routine, the module addressed as slave bit (iaas) should be tested to check if a calling of its own address has just been received. if iaas is set, software should set the transmit/receive mode select bit (tx/rx bit of ibcr) according to the r/w command bit (srw). writing to the ibcr clears the iaas automatically. note that the only time iaas is read as set is from the interrupt at the end of the address cycle where an address match occurred, interrupts resulting from subsequent data transfers will have iaas cleared. a data transfer may now be initiated by writing information to ibdr, for slave transmits, or dummy reading from ibdr, in slave receive mode. the slave will drive scl low in-between byte transfers, scl is released when the ibdr is accessed in the required mode. mastx tst txcnt ;get value from the transmiting counter beq end ;end if no more data brset ibsr,#$01,end ;end if no ack movb databuf,ibdr ;transmit next byte of data dec txcnt ;decrease the txcnt bra emastx ;exit end bclr ibcr,#$20 ;generate a stop condition emastx rti ;return from interrupt masr dec rxcnt ;decrease the rxcnt beq enmasr ;last byte to be read movb rxcnt,d1 ;check second last byte dec d1 ;to be read bne nxmar ;not last or second last lamar bset ibcr,#$08 ;second last, disable ack ;transmitting bra nxmar enmasr bclr ibcr,#$20 ;last one, generate ?top?signal nxmar movb ibdr,rxbuf ;read data and store rti restart bset ibcr,#$04 ;another start (restart) movb calling,ibdr ;transmit the calling address;d0=r/w chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 268 freescale semiconductor in slave transmitter routine, the received acknowledge bit (rxak) must be tested before transmitting the next byte of data. setting rxak means an 'end of data' signal from the master receiver, after which it must be switched from transmitter mode to receiver mode by software. a dummy read then releases the scl line so that the master can generate a stop signal. 8.7.1.7 arbitration lost if several masters try to engage the bus simultaneously, only one master wins and the others lose arbitration. the devices which lost arbitration are immediately switched to slave receive mode by the hardware. their data output to the sda line is stopped, but scl continues to be generated until the end of the byte during which arbitration was lost. an interrupt occurs at the falling edge of the ninth clock of this transfer with ibal=1 and ms/sl=0. if one master attempts to start transmission while the bus is being engaged by another master, the hardware will inhibit the transmission; switch the ms/sl bit from 1 to 0 without generating stop condition; generate an interrupt to cpu and set the ibal to indicate that the attempt to engage the bus is failed. when considering these cases, the slave service routine should test the ibal ?st and the software should clear the ibal bit if it is set. chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 269 figure 8-11. flow-chart of typical iic interrupt routine clear master mode ? tx/rx ? last byte transmitted ? rxak=0 ? end of addr cycle (master rx) ? write next byte to ibdr switch to rx mode dummy read from ibdr generate stop signal read data from ibdr and store set txak =1 generate stop signal 2nd last byte to be read ? last byte to be read ? arbitration lost ? clear ibal iaas=1 ? iaas=1 ? srw=1 ? tx/rx ? set tx mode write data to ibdr set rx mode dummy read from ibdr ack from receiver ? tx next byte read data from ibdr and store switch to rx mode dummy read from ibdr rti yn y y y y y y y y y n n n n n n n n n y tx rx rx tx (write) (read) n ibif address transfer data transfer chapter 8 inter-integrated circuit (iicv2) mc9s12kg128 data sheet, rev. 1.15 270 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 271 chapter 9 freescale s scalable controller area network (mscanv2) 9.1 introduction freescale s scalable controller area network (mscan) de?ition is based on the mscan12 de?ition, which is the speci? implementation of the mscan concept targeted for the m68hc12 microcontroller family. the module is a communication controller implementing the can 2.0a/b protocol as de?ed in the bosch speci?ation dated september 1991. for users to fully understand the mscan speci?ation, it is recommended that the bosch speci?ation be read ?st to familiarize the reader with the terms and concepts contained within this document. though not exclusively intended for automotive applications, can protocol is designed to meet the speci? requirements of a vehicle serial data bus: real-time processing, reliable operation in the emi environment of a vehicle, cost-effectiveness, and required bandwidth. mscan uses an advanced buffer arrangement resulting in predictable real-time behavior and simpli?d application software. 9.1.1 block diagram figure 9-1. mscan block diagram rxcan txcan receive/ transmit engine message filtering and buffering control and status wake-up interrupt req. errors interrupt req. receive interrupt req. transmit interrupt req. canclk bus clock con?uration oscillator clock mux presc. tq clk mscan low pass filter wake-up registers chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 272 freescale semiconductor 9.1.2 features the basic features of the mscan are as follows: implementation of the can protocol ?version 2.0a/b standard and extended data frames zero to eight bytes data length programmable bit rate up to 1 mbps 1 support for remote frames five receive buffers with fifo storage scheme three transmit buffers with internal prioritization using a ?ocal priority?concept flexible maskable identi?r ?ter supports two full-size (32-bit) extended identi?r ?ters, or four 16-bit ?ters, or eight 8-bit ?ters programmable wakeup functionality with integrated low-pass ?ter programmable loopback mode supports self-test operation programmable listen-only mode for monitoring of can bus separate signalling and interrupt capabilities for all can receiver and transmitter error states (warning, error passive, bus-off) programmable mscan clock source either bus clock or oscillator clock internal timer for time-stamping of received and transmitted messages three low-power modes: sleep, power down, and mscan enable global initialization of con?uration registers 9.1.3 modes of operation the following modes of operation are speci? to the mscan. see section 9.4, ?unctional description , for details. listen-only mode mscan sleep mode mscan initialization mode mscan power down mode 9.2 external signal description the mscan uses two external pins: 9.2.1 rxcan ?can receiver input pin rxcan is the mscan receiver input pin. 1. depending on the actual bit timing and the clock jitter of the pll. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 273 9.2.2 txcan ?can transmitter output pin txcan is the mscan transmitter output pin. the txcan output pin represents the logic level on the can bus: 0 = dominant state 1 = recessive state 9.2.3 can system a typical can system with mscan is shown in figure 9-2 . each can station is connected physically to the can bus lines through a transceiver device. the transceiver is capable of driving the large current needed for the can bus and has current protection against defective can or defective stations. figure 9-2. can system 9.3 memory map and register de?ition this section provides a detailed description of all registers accessible in the mscan. 9.3.1 module memory map table 9-1 gives an overview on all registers and their individual bits in the mscan memory map. the register address results from the addition of base address and address offset . the base address is determined at the mcu level and can be found in the memory block description chapter. the address offset is de?ed at the module level. the mscan occupies 64 bytes in the memory space. the base address of the mscan module is determined at the mcu level when the mcu is de?ed. the register decode map is ?ed and begins at the ?st address of the module address offset. table 9-1 shows the individual registers associated with the mscan and their relative offset from the base address. the detailed register descriptions follow in the order they appear in the register map. can bus can controller (mscan) transceiver can node 1 can node 2 can node n can_l can_h mcu txcan rxcan chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 274 freescale semiconductor table 9-1. mscan memory map address offset register access 0x0000 mscan control register 0 (canctl0) r/w 1 1 refer to detailed register description for write access restrictions on per bit basis. 0x0001 mscan control register 1 (canctl1) r/w 1 0x0002 mscan bus timing register 0 (canbtr0) r/w 0x0003 mscan bus timing register 1 (canbtr1) r/w 0x0004 mscan receiver flag register (canrflg) r/w 1 0x0005 mscan receiver interrupt enable register (canrier) r/w 0x0006 mscan transmitter flag register (cantflg) r/w 1 0x0007 mscan transmitter interrupt enable register (cantier) r/w 1 0x0008 mscan transmitter message abort request register (cantarq) r/w 1 0x0009 mscan transmitter message abort acknowledge register (cantaak) r 0x000a mscan transmit buffer selection register (cantbsel) r/w 1 0x000b mscan identi?r acceptance control register (canidac) r/w 1 0x000c reserved 0x000d reserved 0x000e mscan receive error counter (canrxerr) r 0x000f mscan transmit error counter (cantxerr) r 0x0010 mscan identi?r acceptance register 0(canidar0) r/w 0x0011 mscan identi?r acceptance register 1(canidar1) r/w 0x0012 mscan identi?r acceptance register 2 (canidar2) r/w 0x0013 mscan identi?r acceptance register 3 (canidar3) r/w 0x0014 mscan identi?r mask register 0 (canidmr0) r/w 0x0015 mscan identi?r mask register 1 (canidmr1) r/w 0x0016 mscan identi?r mask register 2 (canidmr2) r/w 0x0017 mscan identi?r mask register 3 (canidmr3) r/w 0x0018 mscan identi?r acceptance register 4 (canidar4) r/w 0x0019 mscan identi?r acceptance register 5 (canidar5) r/w 0x001a mscan identi?r acceptance register 6 (canidar6) r/w 0x001b mscan identi?r acceptance register 7 (canidar7) r/w 0x001c mscan identi?r mask register 4 (canidmr4) r/w 0x001d mscan identi?r mask register 5 (canidmr5) r/w 0x001e mscan identi?r mask register 6 (canidmr6) r/w 0x001f mscan identi?r mask register 7 (canidmr7) r/w 0x0020 -0x002f foreground receive buffer (canrxfg) r 2 2 reserved bits and unused bits within the tx- and rx-buffers (cantxfg, canrxfg) will be read as ?? because of ram-based implementation. 0x0030 -0x003f foreground transmit buffer (cantxfg) r 2 /w chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 275 table 9-2. mscan memory map offset address register access 0x0000 this section describes in detail all the registers and register bits in the mscan module. each description includes a standard register diagram with an associated ?ure number. details of register bit and ?ld function follow the register diagrams, in bit order. all bits of all registers in this module are completely synchronous to internal clocks during a register read. r/w 1 1 refer to detailed register description for write access restrictions on per bit basis. 0x0001 mscan control register 1 (canctl1) r/w 1 0x0002 mscan bus timing register 0 (canbtr0) r/w 0x0003 mscan bus timing register 1 (canbtr1) r/w 0x0004 mscan receiver flag register (canrflg) r/w 1 0x0005 mscan receiver interrupt enable register (canrier) r/w 0x0006 mscan transmitter flag register (cantflg) r/w 1 0x0007 mscan transmitter interrupt enable register (cantier) r/w 1 0x0008 mscan transmitter message abort request register (cantarq) r/w 1 0x0009 mscan transmitter message abort acknowledge register (cantaak) r 0x000a mscan transmit buffer selection register (cantbsel) r/w 1 0x000b mscan identi?r acceptance control register (canidac) r/w 1 0x000c reserved 0x000d reserved 0x000e mscan receive error counter (canrxerr) r 0x000f mscan transmit error counter (cantxerr) r 0x0010 mscan identi?r acceptance register 0(canidar0) r/w 0x0011 mscan identi?r acceptance register 1(canidar1) r/w 0x0012 mscan identi?r acceptance register 2 (canidar2) r/w 0x0013 mscan identi?r acceptance register 3 (canidar3) r/w 0x0014 mscan identi?r mask register 0 (canidmr0) r/w 0x0015 mscan identi?r mask register 1 (canidmr1) r/w 0x0016 mscan identi?r mask register 2 (canidmr2) r/w 0x0017 mscan identi?r mask register 3 (canidmr3) r/w 0x0018 mscan identi?r acceptance register 4 (canidar4) r/w 0x0019 mscan identi?r acceptance register 5 (canidar5) r/w 0x001a mscan identi?r acceptance register 6 (canidar6) r/w 0x001b mscan identi?r acceptance register 7 (canidar7) r/w 0x001c mscan identi?r mask register 4 (canidmr4) r/w 0x001d mscan identi?r mask register 5 (canidmr5) r/w 0x001e mscan identi?r mask register 6 (canidmr6) r/w 0x001f mscan identi?r mask register 7 (canidmr7) r/w 0x0020 -0x002f foreground receive buffer (canrxfg) r 2 0x0030 -0x003f foreground transmit buffer (cantxfg) r 2 /w chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 276 freescale semiconductor 9.3.2 register descriptions this section describes in detail all the registers and register bits in the mscan module. each description includes a standard register diagram with an associated ?ure number. details of register bit and ?ld function follow the register diagrams, in bit order. all bits of all registers in this module are completely synchronous to internal clocks during a register read. 9.3.2.1 mscan control register 0 (canctl0) the canctl0 register provides various control bits of the mscan module as described below. note the canctl0 register, except wupe, initrq, and slprq, is held in the reset state when the initialization mode is active (initrq = 1 and initak = 1). this register is writable again as soon as the initialization mode is exited (initrq = 0 and initak = 0). read: anytime write: anytime when out of initialization mode; exceptions are read-only rxact and synch, rxfrm (which is set by the module only), and initrq (which is also writable in initialization mode). 2 reserved bits and unused bits within the tx- and rx-buffers (cantxfg, canrxfg) will be read as ?? because of ram-based implementation. 76543210 r rxfrm rxact cswai synch time wupe slprq initrq w reset: 00000001 = unimplemented figure 9-3. mscan control register 0 (canctl0) table 9-3. canctl0 register field descriptions field description 7 rxfrm 1 received frame flag this bit is read and clear only. it is set when a receiver has received a valid message correctly, independently of the ?ter con?uration. after it is set, it remains set until cleared by software or reset. clearing is done by writing a 1. writing a 0 is ignored. this bit is not valid in loopback mode. 0 no valid message was received since last clearing this ?g 1 a valid message was received since last clearing of this ?g 6 rxact receiver active status ?this read-only ?g indicates the mscan is receiving a message. the ?g is controlled by the receiver front end. this bit is not valid in loopback mode. 0 mscan is transmitting or idle 2 1 mscan is receiving a message (including when arbitration is lost) 2 5 cswai 3 can stops in wait mode enabling this bit allows for lower power consumption in wait mode by disabling all the clocks at the cpu bus interface to the mscan module. 0 the module is not affected during wait mode 1 the module ceases to be clocked during wait mode chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 277 4 synch synchronized status this read-only ?g indicates whether the mscan is synchronized to the can bus and able to participate in the communication process. it is set and cleared by the mscan. 0 mscan is not synchronized to the can bus 1 mscan is synchronized to the can bus 3 time timer enable this bit activates an internal 16-bit wide free running timer which is clocked by the bit clock rate. if the timer is enabled, a 16-bit time stamp will be assigned to each transmitted/received message within the active tx/rx buffer. as soon as a message is acknowledged on the can bus, the time stamp will be written to the highest bytes (0x000e, 0x000f) in the appropriate buffer (see section 9.3.3, ?rogrammer s model of message storage ?. the internal timer is reset (all bits set to 0) when disabled. this bit is held low in initialization mode. 0 disable internal mscan timer 1 enable internal mscan timer 2 wupe 4 wake-up enable this con?uration bit allows the mscan to restart from sleep mode when traf? on can is detected (see section 9.4.6.4, ?scan sleep mode ?. 0 wake-up disabled ?the mscan ignores traf? on can 1 wake-up enabled ?the mscan is able to restart 1 slprq 5 sleep mode request ?this bit requests the mscan to enter sleep mode, which is an internal power saving mode (see section 9.4.6.4, ?scan sleep mode ?. the sleep mode request is serviced when the can bus is idle, i.e., the module is not receiving a message and all transmit buffers are empty. the module indicates entry to sleep mode by setting slpak = 1 (see section 9.3.2.2, ?scan control register 1 (canctl1) ?. sleep mode will be active until slprq is cleared by the cpu or, depending on the setting of wupe, the mscan detects activity on the can bus and clears slprq itself. 0 running ?the mscan functions normally 1 sleep mode request ?the mscan enters sleep mode when can bus idle 0 initrq 6,7 initialization mode request ?when this bit is set by the cpu, the mscan skips to initialization mode (see section 9.4.6.5, ?scan initialization mode ?. any ongoing transmission or reception is aborted and synchronization to the can bus is lost. the module indicates entry to initialization mode by setting initak = 1 ( section 9.3.2.2, ?scan control register 1 (canctl1) ?. the following registers enter their hard reset state and restore their default values: canctl0 8 , canrflg 9 , canrier 10 , cantflg, cantier, cantarq, cantaak, and cantbsel. the registers canctl1, canbtr0, canbtr1, canidac, canidar0-7, and canidmr0-7 can only be written by the cpu when the mscan is in initialization mode (initrq = 1 and initak = 1). the values of the error counters are not affected by initialization mode. when this bit is cleared by the cpu, the mscan restarts and then tries to synchronize to the can bus. if the mscan is not in bus-off state, it synchronizes after 11 consecutive recessive bits on the can bus; if the mscan is in bus-off state, it continues to wait for 128 occurrences of 11 consecutive recessive bits. writing to other bits in canctl0, canrflg, canrier, cantflg, or cantier must be done only after initialization mode is exited, which is initrq = 0 and initak = 0. 0 normal operation 1 mscan in initialization mode 1 the mscan must be in normal mode for this bit to become set. 2 see the bosch can 2.0a/b speci?ation for a detailed de?ition of transmitter and receiver states. 3 in order to protect from accidentally violating the can protocol, the txcan pin is immediately forced to a recessive state when the cpu enters wait (cswai = 1) or stop mode (see section 9.4.6.2, ?peration in wait mode and section 9.4.6.3, ?peration in stop mode ? . 4 the cpu has to make sure that the wupe register and the wupie wake-up interrupt enable register (see section 9.3.2.6, ?scan receiver interrupt enable register (canrier) ) is enabled, if the recovery mechanism from stop or wait is required. 5 the cpu cannot clear slprq before the mscan has entered sleep mode (slprq = 1 and slpak = 1). 6 the cpu cannot clear initrq before the mscan has entered initialization mode (initrq = 1 and initak = 1). 7 in order to protect from accidentally violating the can protocol, the txcan pin is immediately forced to a recessive state when the initialization mode is requested by the cpu. thus, the recommended procedure is to bring the mscan into sleep mode (slprq = 1 and slpak = 1) before requesting initialization mode. table 9-3. canctl0 register field descriptions (continued) field description chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 278 freescale semiconductor 9.3.2.2 mscan control register 1 (canctl1) the canctl1 register provides various control bits and handshake status information of the mscan module as described below. read: anytime write: anytime when initrq = 1 and initak = 1, except cane which is write once in normal and anytime in special system operation modes when the mscan is in initialization mode (initrq = 1 and initak = 1). 8 not including wupe, initrq, and slprq. 9 tstat1 and tstat0 are not affected by initialization mode. 10 rstat1 and rstat0 are not affected by initialization mode. table 9-4. canctl1 register field descriptions field description 7 cane mscan enable 0 mscan module is disabled 1 mscan module is enabled 6 clksrc mscan clock source this bit de?es the clock source for the mscan module (only for systems with a clock generation module; section 9.4.3.2, ?lock system , and section figure 9-40., ?scan clocking scheme ,?. 0 mscan clock source is the oscillator clock 1 mscan clock source is the bus clock 5 loopb loopback self test mode when this bit is set, the mscan performs an internal loopback which can be used for self test operation. the bit stream output of the transmitter is fed back to the receiver internally. the rxcan input pin is ignored and the txcan output goes to the recessive state (logic 1). the mscan behaves as it does normally when transmitting and treats its own transmitted message as a message received from a remote node. in this state, the mscan ignores the bit sent during the ack slot in the can frame acknowledge ?ld to ensure proper reception of its own message. both transmit and receive interrupts are generated. 0 loopback self test disabled 1 loopback self test enabled 4 listen listen only mode this bit con?ures the mscan as a can bus monitor. when listen is set, all valid can messages with matching id are received, but no acknowledgement or error frames are sent out (see section 9.4.5.4, ?isten-only mode ?. in addition, the error counters are frozen. listen only mode supports applications which require ?ot plugging?or throughput analysis. the mscan is unable to transmit any messages when listen only mode is active. 0 normal operation 1 listen only mode activated 2 wupm wake-up mode ?if wupe in canctl0 is enabled, this bit de?es whether the integrated low-pass ?ter is applied to protect the mscan from spurious wake-up (see section 9.4.6.4, ?scan sleep mode ?. 0 mscan wakes up the cpu after any recessive to dominant edge on the can bus 1 mscan wakes up the cpu only in case of a dominant pulse on the can bus that has a length of t wup chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 279 1 slpak sleep mode acknowledge ?this ?g indicates whether the mscan module has entered sleep mode (see section 9.4.6.4, ?scan sleep mode ?. it is used as a handshake ?g for the slprq sleep mode request. sleep mode is active when slprq = 1 and slpak = 1. depending on the setting of wupe, the mscan will clear the ?g if it detects activity on the can bus while in sleep mode. 0 running ?the mscan operates normally 1 sleep mode active ?the mscan has entered sleep mode 0 initak initialization mode acknowledge ?this ?g indicates whether the mscan module is in initialization mode (see section 9.4.6.5, ?scan initialization mode ?. it is used as a handshake ?g for the initrq initialization mode request. initialization mode is active when initrq = 1 and initak = 1. the registers canctl1, canbtr0, canbtr1, canidac, canidar0?anidar7, and canidmr0?anidmr7 can be written only by the cpu when the mscan is in initialization mode. 0 running ?the mscan operates normally 1 initialization mode active ?the mscan has entered initialization mode table 9-4. canctl1 register field descriptions (continued) field description chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 280 freescale semiconductor 9.3.2.3 mscan bus timing register 0 (canbtr0) the canbtr0 register con?ures various can bus timing parameters of the mscan module. read: anytime write: anytime in initialization mode (initrq = 1 and initak = 1) 76543210 r sjw1 sjw0 brp5 brp4 brp3 brp2 brp1 brp0 w reset: 00000000 figure 9-4. mscan bus timing register 0 (canbtr 0 ) table 9-5. canbtr 0 register field descriptions field description 7:6 sjw[1:0] synchronization jump width the synchronization jump width de?es the maximum number of time quanta (tq) clock cycles a bit can be shortened or lengthened to achieve resynchronization to data transitions on the can bus (see table 9-6 ). 5:0 brp[5:0] baud rate prescaler these bits determine the time quanta (tq) clock which is used to build up the bit timing (see table 9-7 ). table 9-6. synchronization jump width sjw1 sjw0 synchronization jump width 0 0 1 tq clock cycle 0 1 2 tq clock cycles 1 0 3 tq clock cycles 1 1 4 tq clock cycles table 9-7. baud rate prescaler brp5 brp4 brp3 brp2 brp1 brp0 prescaler value (p) 000000 1 000001 2 000010 3 000011 4 :::::: : 111111 64 chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 281 9.3.2.4 mscan bus timing register 1 (canbtr1) the canbtr1 register con?ures various can bus timing parameters of the mscan module. read: anytime write: anytime in initialization mode (initrq = 1 and initak = 1) 76543210 r samp tseg22 tseg21 tseg20 tseg13 tseg12 tseg11 tseg10 w reset: 00000000 figure 9-5. mscan bus timing register 1 (canbtr1) table 9-8. canbtr1 register field descriptions field description 7 samp sampling ?this bit determines the number of can bus samples taken per bit time. 0 one sample per bit. 1 three samples per bit 1 . if samp = 0, the resulting bit value is equal to the value of the single bit positioned at the sample point. if samp = 1, the resulting bit value is determined by using majority rule on the three total samples. for higher bit rates, it is recommended that only one sample is taken per bit time (samp = 0). 1 in this case, phase_seg1 must be at least 2 time quanta (tq). 6:4 tseg2[2:0] time segment 2 time segments within the bit time ? the number of clock cycles per bit time and the location of the sample point (see figure 9-41 ). time segment 2 (tseg2) values are programmable as shown in table 9-9 . 3:0 tseg1[3:0] time segment 1 time segments within the bit time ? the number of clock cycles per bit time and the location of the sample point (see figure 9-41 ). time segment 1 (tseg1) values are programmable as shown in table 9-10 . table 9-9. time segment 2 values tseg22 tseg21 tseg20 time segment 2 0 0 0 1 tq clock cycle 1 1 this setting is not valid. please refer to table 9-36 for valid settings. 0 0 1 2 tq clock cycles ::: : 1 1 0 7 tq clock cycles 1 1 1 8 tq clock cycles chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 282 freescale semiconductor the bit time is determined by the oscillator frequency, the baud rate prescaler, and the number of time quanta (tq) clock cycles per bit (as shown in table 9-9 and table 9-10 ). eqn. 9-1 9.3.2.5 mscan receiver flag register (canrflg) a ?g can be cleared only by software (writing a 1 to the corresponding bit position) when the condition which caused the setting is no longer valid. every ?g has an associated interrupt enable bit in the canrier register. note the canrflg register is held in the reset state 1 when the initialization mode is active (initrq = 1 and initak = 1). this register is writable again as soon as the initialization mode is exited (initrq = 0 and initak = 0). read: anytime write: anytime when out of initialization mode, except rstat[1:0] and tstat[1:0] ?gs which are read-only; write of 1 clears ?g; write of 0 is ignored. table 9-10. time segment 1 values tseg13 tseg12 tseg11 tseg10 time segment 1 0 0 0 0 1 tq clock cycle 1 1 this setting is not valid. please refer to table 9-36 for valid settings. 0 0 0 1 2 tq clock cycles 1 0 0 1 0 3 tq clock cycles 1 0 0 1 1 4 tq clock cycles :::: : 1 1 1 0 15 tq clock cycles 1 1 1 1 16 tq clock cycles 76543210 r wupif cscif rstat1 rstat0 tstat1 tstat0 ovrif rxf w reset: 00000000 = unimplemented figure 9-6. mscan receiver flag register (canrflg) 1. the rstat[1:0], tstat[1:0] bits are not affected by initialization mode. bit time prescaler value () f canclk ----------------------------------------------------- - 1 timesegment1 timesegment2 ++ () ? = chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 283 table 9-11. canrflg register field descriptions field description 7 wupif wake-up interrupt flag ?if the mscan detects can bus activity while in sleep mode (see section 9.4.6.4, ?scan sleep mode ,? and wupe = 1 in cantctl0 (see section 9.3.2.1, ?scan control register 0 (canctl0) ?, the module will set wupif. if not masked, a wake-up interrupt is pending while this ?g is set. 0 no wake-up activity observed while in sleep mode 1 mscan detected activity on the can bus and requested wake-up 6 cscif can status change interrupt flag ?this ?g is set when the mscan changes its current can bus status due to the actual value of the transmit error counter (tec) and the receive error counter (rec). an additional 4-bit (rstat[1:0], tstat[1:0]) status register, which is split into separate sections for tec/rec, informs the system on the actual can bus status (see section 9.3.2.6, ?scan receiver interrupt enable register (canrier) ?. if not masked, an error interrupt is pending while this ?g is set. cscif provides a blocking interrupt. that guarantees that the receiver/transmitter status bits (rstat/tstat) are only updated when no can status change interrupt is pending. if the tecs/recs change their current value after the cscif is asserted, which would cause an additional state change in the rstat/tstat bits, these bits keep their status until the current cscif interrupt is cleared again. 0 no change in can bus status occurred since last interrupt 1 mscan changed current can bus status 5:4 rstat[1:0] receiver status bits ?the values of the error counters control the actual can bus status of the mscan. as soon as the status change interrupt ?g (cscif) is set, these bits indicate the appropriate receiver related can bus status of the mscan. the coding for the bits rstat1, rstat0 is: 00 rxok: 0 receive error counter 96 01 rxwrn: 96 < receive error counter 127 10 rxerr: 127 < receive error counter 11 bus-off 1 : transmit error counter > 255 1 redundant information for the most critical can bus status which is ?us-off? this only occurs if the tx error counter exceeds a number of 255 errors. bus-off affects the receiver state. as soon as the transmitter leaves its bus-off state the receiver state skips to rxok too. refer also to tstat[1:0] coding in this register. 3:2 tstat[1:0] transmitter status bits ?the values of the error counters control the actual can bus status of the mscan. as soon as the status change interrupt ?g (cscif) is set, these bits indicate the appropriate transmitter related can bus status of the mscan. the coding for the bits tstat1, tstat0 is: 00 txok: 0 transmit error counter 96 01 txwrn: 96 < transmit error counter 127 10 txerr: 127 < transmit error counter 255 11 bus-off: transmit error counter > 255 1 ovrif overrun interrupt flag this ?g is set when a data overrun condition occurs. if not masked, an error interrupt is pending while this ?g is set. 0 no data overrun condition 1 a data overrun detected 0 rxf 2 2 to ensure data integrity, do not read the receive buffer registers while the rxf ?g is cleared. for mcus with dual cpus, reading the receive buffer registers while the rxf ?g is cleared may result in a cpu fault condition. receive buffer full flag rxf is set by the mscan when a new message is shifted in the receiver fifo. this ?g indicates whether the shifted buffer is loaded with a correctly received message (matching identi?r, matching cyclic redundancy code (crc) and no other errors detected). after the cpu has read that message from the rxfg buffer in the receiver fifo, the rxf ?g must be cleared to release the buffer. a set rxf ?g prohibits the shifting of the next fifo entry into the foreground buffer (rxfg). if not masked, a receive interrupt is pending while this ?g is set. 0 no new message available within the rxfg 1 the receiver fifo is not empty. a new message is available in the rxfg chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 284 freescale semiconductor 9.3.2.6 mscan receiver interrupt enable register (canrier) this register contains the interrupt enable bits for the interrupt ?gs described in the canrflg register. note the canrier register is held in the reset state when the initialization mode is active (initrq=1 and initak=1). this register is writable when not in initialization mode (initrq=0 and initak=0). the rstate[1:0], tstate[1:0] bits are not affected by initialization mode. read: anytime write: anytime when not in initialization mode 76543210 r wupie cscie rstate1 rstate0 tstate1 tstate0 ovrie rxfie w reset: 00000000 figure 9-7. mscan receiver interrupt enable register (canrier) table 9-12. canrier register field descriptions field description 7 wupie 1 wake-up interrupt enable 0 no interrupt request is generated from this event. 1 a wake-up event causes a wake-up interrupt request. 6 cscie can status change interrupt enable 0 no interrupt request is generated from this event. 1 a can status change event causes an error interrupt request. 5:4 rstate[1:0] receiver status change enable these rstat enable bits control the sensitivity level in which receiver state changes are causing cscif interrupts. independent of the chosen sensitivity level the rstat ?gs continue to indicate the actual receiver state and are only updated if no cscif interrupt is pending. 00 do not generate any cscif interrupt caused by receiver state changes. 01 generate cscif interrupt only if the receiver enters or leaves ?us-off?state. discard other receiver state changes for generating cscif interrupt. 10 generate cscif interrupt only if the receiver enters or leaves ?xerr?or ?us-off 2 state. discard other receiver state changes for generating cscif interrupt. 11 generate cscif interrupt on all state changes. 3:2 tstate[1:0] transmitter status change enable these tstat enable bits control the sensitivity level in which transmitter state changes are causing cscif interrupts. independent of the chosen sensitivity level, the tstat ?gs continue to indicate the actual transmitter state and are only updated if no cscif interrupt is pending. 00 do not generate any cscif interrupt caused by transmitter state changes. 01 generate cscif interrupt only if the transmitter enters or leaves ?us-off?state. discard other transmitter state changes for generating cscif interrupt. 10 generate cscif interrupt only if the transmitter enters or leaves ?xerr?or ?us-off?state. discard other transmitter state changes for generating cscif interrupt. 11 generate cscif interrupt on all state changes. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 285 9.3.2.7 mscan transmitter flag register (cantflg) the transmit buffer empty ?gs each have an associated interrupt enable bit in the cantier register. note the cantflg register is held in the reset state when the initialization mode is active (initrq = 1 and initak = 1). this register is writable when not in initialization mode (initrq = 0 and initak = 0). read: anytime write: anytime for txex ?gs when not in initialization mode; write of 1 clears ?g, write of 0 is ignored 1 ovrie overrun interrupt enable 0 no interrupt request is generated from this event. 1 an overrun event causes an error interrupt request. 0 rxfie receiver full interrupt enable 0 no interrupt request is generated from this event. 1 a receive buffer full (successful message reception) event causes a receiver interrupt request. 1 wupie and wupe (see section 9.3.2.1, ?scan control register 0 (canctl0) ? must both be enabled if the recovery mechanism from stop or wait is required. 2 bus-off state is de?ed by the can standard (see bosch can 2.0a/b protocol speci?ation: for only transmitters. because the only possible state change for the transmitter from bus-off to txok also forces the receiver to skip its current state to rxok, the coding of the rxstat[1:0] ?gs de?e an additional bus-off state for the receiver (see section 9.3.2.5, ?scan receiver flag register (canrflg) ?. 76543210 r0 0 0 00 txe2 txe1 txe0 w reset: 00000111 = unimplemented figure 9-8. mscan transmitter flag register (cantflg) table 9-12. canrier register field descriptions (continued) field description chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 286 freescale semiconductor 9.3.2.8 mscan transmitter interrupt enable register (cantier) this register contains the interrupt enable bits for the transmit buffer empty interrupt ?gs. note the cantier register is held in the reset state when the initialization mode is active (initrq = 1 and initak = 1). this register is writable when not in initialization mode (initrq = 0 and initak = 0). read: anytime write: anytime when not in initialization mode table 9-13. cantflg register field descriptions field description 2:0 txe[2:0] transmitter buffer empty this ?g indicates that the associated transmit message buffer is empty, and thus not scheduled for transmission. the cpu must clear the ?g after a message is set up in the transmit buffer and is due for transmission. the mscan sets the ?g after the message is sent successfully. the ?g is also set by the mscan when the transmission request is successfully aborted due to a pending abort request (see section 9.3.2.9, ?scan transmitter message abort request register (cantarq) ?. if not masked, a transmit interrupt is pending while this ?g is set. clearing a txex ?g also clears the corresponding abtakx (see section 9.3.2.10, ?scan transmitter message abort acknowledge register (cantaak) ?. when a txex ?g is set, the corresponding abtrqx bit is cleared (see section 9.3.2.9, ?scan transmitter message abort request register (cantarq) ?. when listen-mode is active (see section 9.3.2.2, ?scan control register 1 (canctl1) ? the txex ?gs cannot be cleared and no transmission is started. read and write accesses to the transmit buffer will be blocked, if the corresponding txex bit is cleared (txex = 0) and the buffer is scheduled for transmission. 0 the associated message buffer is full (loaded with a message due for transmission) 1 the associated message buffer is empty (not scheduled) 76543210 r00000 txeie2 txeie1 txeie0 w reset: 00000000 = unimplemented figure 9-9. mscan transmitter interrupt enable register (cantier) table 9-14. cantier register field descriptions field description 2:0 txeie[2:0] transmitter empty interrupt enable 0 no interrupt request is generated from this event. 1 a transmitter empty (transmit buffer available for transmission) event causes a transmitter empty interrupt request. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 287 9.3.2.9 mscan transmitter message abort request register (cantarq) the cantarq register allows abort request of queued messages as described below. note the cantarq register is held in the reset state when the initialization mode is active (initrq = 1 and initak = 1). this register is writable when not in initialization mode (initrq = 0 and initak = 0). read: anytime write: anytime when not in initialization mode 76543210 r00000 abtrq2 abtrq1 abtrq0 w reset: 00000000 = unimplemented figure 9-10. mscan transmitter message abort request register (cantarq) table 9-15. cantarq register field descriptions field description 2:0 abtrq[2:0] abort request ?the cpu sets the abtrqx bit to request that a scheduled message buffer (txex = 0) be aborted. the mscan grants the request if the message has not already started transmission, or if the transmission is not successful (lost arbitration or error). when a message is aborted, the associated txe (see section 9.3.2.7, ?scan transmitter flag register (cantflg) ? and abort acknowledge ?gs (abtak, see section 9.3.2.10, ?scan transmitter message abort acknowledge register (cantaak) ? are set and a transmit interrupt occurs if enabled. the cpu cannot reset abtrqx. abtrqx is reset whenever the associated txe ?g is set. 0 no abort request 1 abort request pending chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 288 freescale semiconductor 9.3.2.10 mscan transmitter message abort acknowledge register (cantaak) the cantaak register indicates the successful abort of a queued message, if requested by the appropriate bits in the cantarq register. note the cantaak register is held in the reset state when the initialization mode is active (initrq = 1 and initak = 1). read: anytime write: unimplemented for abtakx ?gs 76543210 r00000 abtak2 abtak1 abtak0 w reset: 00000000 = unimplemented figure 9-11. mscan transmitter message abort acknowledge register (cantaak) table 9-16. cantaak register field descriptions field description 2:0 abtak[2:0] abort acknowledge ?this ?g acknowledges that a message was aborted due to a pending abort request from the cpu. after a particular message buffer is ?gged empty, this ?g can be used by the application software to identify whether the message was aborted successfully or was sent anyway. the abtakx ?g is cleared whenever the corresponding txe ?g is cleared. 0 the message was not aborted. 1 the message was aborted. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 289 9.3.2.11 mscan transmit buffer selection register (cantbsel) the cantbsel register allows the selection of the actual transmit message buffer, which then will be accessible in the cantxfg register space. note the cantbsel register is held in the reset state when the initialization mode is active (initrq = 1 and initak=1). this register is writable when not in initialization mode (initrq = 0 and initak = 0). read: find the lowest ordered bit set to 1, all other bits will be read as 0 write: anytime when not in initialization mode the following gives a short programming example of the usage of the cantbsel register: to get the next available transmit buffer, application software must read the cantflg register and write this value back into the cantbsel register. in this example tx buffers tx1 and tx2 are available. the value read from cantflg is therefore 0b0000_0110. when writing this value back to cantbsel, the tx buffer tx1 is selected in the cantxfg because the lowest numbered bit set to 1 is at bit position 1. reading back this value out of cantbsel results in 0b0000_0010, because only the lowest numbered bit position set to 1 is presented. this mechanism eases the application software the selection of the next available tx buffer. ldd cantflg; value read is 0b0000_0110 std cantbsel; value written is 0b0000_0110 ldd cantbsel; value read is 0b0000_0010 if all transmit message buffers are deselected, no accesses are allowed to the cantxfg registers. 76543210 r00000 tx2 tx1 tx0 w reset: 00000000 = unimplemented figure 9-12. mscan transmit buffer selection register (cantbsel) table 9-17. cantbsel register field descriptions field description 2:0 tx[2:0] transmit buffer select ?the lowest numbered bit places the respective transmit buffer in the cantxfg register space (e.g., tx1 = 1 and tx0 = 1 selects transmit buffer tx0; tx1 = 1 and tx0 = 0 selects transmit buffer tx1). read and write accesses to the selected transmit buffer will be blocked, if the corresponding txex bit is cleared and the buffer is scheduled for transmission (see section 9.3.2.7, ?scan transmitter flag register (cantflg) ?. 0 the associated message buffer is deselected 1 the associated message buffer is selected, if lowest numbered bit chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 290 freescale semiconductor 9.3.2.12 mscan identi?r acceptance control register (canidac) the canidac register is used for identi?r acceptance control as described below. read: anytime write: anytime in initialization mode (initrq = 1 and initak = 1), except bits idhitx, which are read-only the idhitx indicators are always related to the message in the foreground buffer (rxfg). when a message gets shifted into the foreground buffer of the receiver fifo the indicators are updated as well. 76543210 r0 0 idam1 idam0 0 idhit2 idhit1 idhit0 w reset: 00000000 = unimplemented figure 9-13. mscan identi?r acceptance control register (canidac) table 9-18. canidac register field descriptions field description 5:4 idam[1:0] identi?r acceptance mode the cpu sets these ?gs to de?e the identi?r acceptance ?ter organization (see section 9.4.3, ?denti?r acceptance filter ?. table 9-19 summarizes the different settings. in ?ter closed mode, no message is accepted such that the foreground buffer is never reloaded. 2:0 idhit[2:0] identi?r acceptance hit indicator ?the mscan sets these ?gs to indicate an identi?r acceptance hit (see section 9.4.3, ?denti?r acceptance filter ?. table 9-20 summarizes the different settings. table 9-19. identi?r acceptance mode settings idam1 idam0 identi?r acceptance mode 0 0 two 32-bit acceptance ?ters 0 1 four 16-bit acceptance ?ters 1 0 eight 8-bit acceptance ?ters 1 1 filter closed table 9-20. identi?r acceptance hit indication idhit2 idhit1 idhit0 identi?r acceptance hit 0 0 0 filter 0 hit 0 0 1 filter 1 hit 0 1 0 filter 2 hit 0 1 1 filter 3 hit 1 0 0 filter 4 hit 1 0 1 filter 5 hit 1 1 0 filter 6 hit 1 1 1 filter 7 hit chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 291 9.3.2.13 mscan reserved register reserved for factory testing of the mscan module and is not available in normal system operation modes. read: always read 0x0000 in normal system operation modes write: unimplemented in normal system operation modes note writing to this register when in special modes can alter the mscan functionality. 9.3.2.14 mscan receive error counter (canrxerr) this register re?cts the status of the mscan receive error counter. read: only when in sleep mode (slprq = 1 and slpak = 1) or initialization mode (initrq = 1 and initak = 1) write: unimplemented note reading this register when in any other mode other than sleep or initialization mode may return an incorrect value. for mcus with dual cpus, this may result in a cpu fault condition. writing to this register when in special modes can alter the mscan functionality. 76543210 r00000000 w reset: 00000000 = unimplemented figure 9-14. mscan reserved register 76543210 r rxerr7 rxerr6 rxerr5 rxerr4 rxerr3 rxerr2 rxerr1 rxerr0 w reset: 00000000 = unimplemented figure 9-15. mscan receive error counter (canrxerr) chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 292 freescale semiconductor 9.3.2.15 mscan transmit error counter (cantxerr) this register re?cts the status of the mscan transmit error counter. read: only when in sleep mode (slprq = 1 and slpak = 1) or initialization mode (initrq = 1 and initak = 1) write: unimplemented note reading this register when in any other mode other than sleep or initialization mode, may return an incorrect value. for mcus with dual cpus, this may result in a cpu fault condition. writing to this register when in special modes can alter the mscan functionality. 76543210 r txerr7 txerr6 txerr5 txerr4 txerr3 txerr2 txerr1 txerr0 w reset: 00000000 = unimplemented figure 9-16. mscan transmit error counter (cantxerr) chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 293 9.3.2.16 mscan identi?r acceptance registers (canidar0-7) on reception, each message is written into the background receive buffer. the cpu is only signalled to read the message if it passes the criteria in the identi?r acceptance and identi?r mask registers (accepted); otherwise, the message is overwritten by the next message (dropped). the acceptance registers of the mscan are applied on the idr0?dr3 registers (see section 9.3.3.1, ?denti?r registers (idr0?dr3) ? of incoming messages in a bit by bit manner (see section 9.4.3, ?denti?r acceptance filter ?. for extended identi?rs, all four acceptance and mask registers are applied. for standard identi?rs, only the ?st two (canidar0/1, canidmr0/1) are applied. read: anytime write: anytime in initialization mode (initrq = 1 and initak = 1) module base + 0x0010 (canidar0) 0x0011 (canidar1) 0x0012 (canidar2) 0x0013 (canidar3) 76543210 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w reset 00000000 76543210 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w reset 00000000 76543210 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w reset 00000000 76543210 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w reset 00000000 figure 9-17. mscan identi?r acceptance registers (first bank) ?canidar0?anidar3 table 9-21. canidar0?anidar3 register field descriptions field description 7:0 ac[7:0] acceptance code bits ac[7:0] comprise a user-de?ed sequence of bits with which the corresponding bits of the related identi?r register (idrn) of the receive message buffer are compared. the result of this comparison is then masked with the corresponding identi?r mask register. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 294 freescale semiconductor read: anytime write: anytime in initialization mode (initrq = 1 and initak = 1) module base + 0x0018 (canidar4) 0x0019 (canidar5) 0x001a (canidar6) 0x001b (canidar7) 76543210 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w reset 00000000 76543210 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w reset 00000000 76543210 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w reset 00000000 76543210 r ac7 ac6 ac5 ac4 ac3 ac2 ac1 ac0 w reset 00000000 figure 9-18. mscan identi?r acceptance registers (second bank) ?canidar4?anidar7 table 9-22. canidar4?anidar7 register field descriptions field description 7:0 ac[7:0] acceptance code bits ac[7:0] comprise a user-de?ed sequence of bits with which the corresponding bits of the related identi?r register (idrn) of the receive message buffer are compared. the result of this comparison is then masked with the corresponding identi?r mask register. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 295 9.3.2.17 mscan identi?r mask registers (canidmr0?anidmr7) the identi?r mask register speci?s which of the corresponding bits in the identi?r acceptance register are relevant for acceptance ?tering. to receive standard identi?rs in 32 bit ?ter mode, it is required to program the last three bits (am[2:0]) in the mask registers canidmr1 and canidmr5 to ?on t care. to receive standard identi?rs in 16 bit ?ter mode, it is required to program the last three bits (am[2:0]) in the mask registers canidmr1, canidmr3, canidmr5, and canidmr7 to ?on t care. read: anytime write: anytime in initialization mode (initrq = 1 and initak = 1) module base + 0x0014 (canidmr0) 0x0015 (canidmr1) 0x0016 (canidmr2) 0x0017 (canidmr3) 76543210 r am7 am6 am5 am4 am3 am2 am1 am0 w reset 00000000 76543210 r am7 am6 am5 am4 am3 am2 am1 am0 w reset 00000000 76543210 r am7 am6 am5 am4 am3 am2 am1 am0 w reset 00000000 76543210 r am7 am6 am5 am4 am3 am2 am1 am0 w reset 00000000 figure 9-19. mscan identi?r mask registers (first bank) ?canidmr0?anidmr3 table 9-23. canidmr0?anidmr3 register field descriptions field description 7:0 am[7:0] acceptance mask bits if a particular bit in this register is cleared, this indicates that the corresponding bit in the identi?r acceptance register must be the same as its identi?r bit before a match is detected. the message is accepted if all such bits match. if a bit is set, it indicates that the state of the corresponding bit in the identi?r acceptance register does not affect whether or not the message is accepted. 0 match corresponding acceptance code register and identi?r bits 1 ignore corresponding acceptance code register bit chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 296 freescale semiconductor read: anytime write: anytime in initialization mode (initrq = 1 and initak = 1) module base + 0x001c (canidmr4) 0x001d (canidmr5) 0x001e (canidmr6) 0x001f (canidmr7) 76543210 r am7 am6 am5 am4 am3 am2 am1 am0 w reset 00000000 76543210 r am7 am6 am5 am4 am3 am2 am1 am0 w reset 00000000 76543210 r am7 am6 am5 am4 am3 am2 am1 am0 w reset 00000000 76543210 r am7 am6 am5 am4 am3 am2 am1 am0 w reset 00000000 figure 9-20. mscan identi?r mask registers (second bank) ?canidmr4?anidmr7 table 9-24. canidmr4?anidmr7 register field descriptions field description 7:0 am[7:0] acceptance mask bits if a particular bit in this register is cleared, this indicates that the corresponding bit in the identi?r acceptance register must be the same as its identi?r bit before a match is detected. the message is accepted if all such bits match. if a bit is set, it indicates that the state of the corresponding bit in the identi?r acceptance register does not affect whether or not the message is accepted. 0 match corresponding acceptance code register and identi?r bits 1 ignore corresponding acceptance code register bit chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 297 9.3.3 programmer s model of message storage the following section details the organization of the receive and transmit message buffers and the associated control registers. to simplify the programmer interface, the receive and transmit message buffers have the same outline. each message buffer allocates 16 bytes in the memory map containing a 13 byte data structure. an additional transmit buffer priority register (tbpr) is de?ed for the transmit buffers. within the last two bytes of this memory map, the mscan stores a special 16-bit time stamp, which is sampled from an internal timer after successful transmission or reception of a message. this feature is only available for transmit and receiver buffers, if the time bit is set (see section 9.3.2.1, ?scan control register 0 (canctl0) ?. the time stamp register is written by the mscan. the cpu can only read these registers. figure 9-21 shows the common 13-byte data structure of receive and transmit buffers for extended identi?rs. the mapping of standard identi?rs into the idr registers is shown in figure 9-22 . all bits of the receive and transmit buffers are ??out of reset because of ram-based implementation 1 . all reserved or unused bits of the receive and transmit buffers always read ?? table 9-25. message buffer organization offset address register access 0x00x0 identi?r register 0 0x00x1 identi?r register 1 0x00x2 identi?r register 2 0x00x3 identi?r register 3 0x00x4 data segment register 0 0x00x5 data segment register 1 0x00x6 data segment register 2 0x00x7 data segment register 3 0x00x8 data segment register 4 0x00x9 data segment register 5 0x00xa data segment register 6 0x00xb data segment register 7 0x00xc data length register 0x00xd transmit buffer priority register 1 1 not applicable for receive buffers 0x00xe time stamp register (high byte) 2 2 read-only for cpu 0x00xf time stamp register (low byte) 3 3 read-only for cpu 1. exception: the transmit priority registers are 0 out of reset. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 298 freescale semiconductor read: for transmit buffers, anytime when txex ?g is set (see section 9.3.2.7, ?scan transmitter flag register (cantflg) ? and the corresponding transmit buffer is selected in cantbsel (see section 9.3.2.11, ?scan transmit buffer selection register (cantbsel) ?. for receive buffers, only when rxf ?g is set (see section 9.3.2.5, ?scan receiver flag register (canrflg) ?. register name bit 7 654321 bit0 idr0 r id28 id27 id26 id25 id24 id23 id22 id21 w idr1 r id20 id19 id18 srr (=1) ide (=1) id17 id16 id15 w idr2 r id14 id13 id12 id11 id10 id9 id8 id7 w idr3 r id6 id5 id4 id3 id2 id1 id0 rtr w dsr0 r db7 db6 db5 db4 db3 db2 db1 db0 w dsr1 r db7 db6 db5 db4 db3 db2 db1 db0 w dsr2 r db7 db6 db5 db4 db3 db2 db1 db0 w dsr3 r db7 db6 db5 db4 db3 db2 db1 db0 w dsr4 r db7 db6 db5 db4 db3 db2 db1 db0 w dsr5 r db7 db6 db5 db4 db3 db2 db1 db0 w dsr6 r db7 db6 db5 db4 db3 db2 db1 db0 w dsr7 r db7 db6 db5 db4 db3 db2 db1 db0 w dlr r dlc3 dlc2 dlc1 dlc0 w = unused, always read ? figure 9-21. receive/transmit message buffer ?extended identi?r mapping chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 299 write: for transmit buffers, anytime when txex ?g is set (see section 9.3.2.7, ?scan transmitter flag register (cantflg) ? and the corresponding transmit buffer is selected in cantbsel (see section 9.3.2.11, ?scan transmit buffer selection register (cantbsel) ?. unimplemented for receive buffers. reset: unde?ed (0x00xx) because of ram-based implementation 9.3.3.1 identi?r registers (idr0?dr3) the identi?r registers for an extended format identi?r consist of a total of 32 bits; id[28:0], srr, ide, and rtr bits. the identi?r registers for a standard format identi?r consist of a total of 13 bits; id[10:0], rtr, and ide bits. 9.3.3.1.1 idr0?dr3 for extended identi?r mapping register name bit 7 654321 bit 0 idr0 r id10 id9 id8 id7 id6 id5 id4 id3 w idr1 r id2 id1 id0 rtr ide (=0) w idr2 r w idr3 r w = unused, always read ? figure 9-22. receive/transmit message buffer ?standard identi?r mapping 76543210 r id28 id27 id26 id25 id24 id23 id22 id21 w reset: xxxxxxxx figure 9-23. identi?r register 0 (idr0) ?extended identi?r mapping table 9-26. idr0 register field descriptions ?extended field description 7:0 id[28:21] extended format identi?r the identi?rs consist of 29 bits (id[28:0]) for the extended format. id28 is the most signi?ant bit and is transmitted ?st on the can bus during the arbitration procedure. the priority of an identi?r is de?ed to be highest for the smallest binary number. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 300 freescale semiconductor 76543210 r id20 id19 id18 srr (=1) ide (=1) id17 id16 id15 w reset: xxxxxxxx figure 9-24. identi?r register 1 (idr1) ?extended identi?r mapping table 9-27. idr1 register field descriptions ?extended field description 7:5 id[20:18] extended format identi?r the identi?rs consist of 29 bits (id[28:0]) for the extended format. id28 is the most signi?ant bit and is transmitted ?st on the can bus during the arbitration procedure. the priority of an identi?r is de?ed to be highest for the smallest binary number. 4 srr substitute remote request ?this ?ed recessive bit is used only in extended format. it must be set to 1 by the user for transmission buffers and is stored as received on the can bus for receive buffers. 3 ide id extended this ?g indicates whether the extended or standard identi?r format is applied in this buffer. in the case of a receive buffer, the ?g is set as received and indicates to the cpu how to process the buffer identi?r registers. in the case of a transmit buffer, the ?g indicates to the mscan what type of identi?r to send. 0 standard format (11 bit) 1 extended format (29 bit) 2:0 id[17:15] extended format identi?r the identi?rs consist of 29 bits (id[28:0]) for the extended format. id28 is the most signi?ant bit and is transmitted ?st on the can bus during the arbitration procedure. the priority of an identi?r is de?ed to be highest for the smallest binary number. 76543210 r id14 id13 id12 id11 id10 id9 id8 id7 w reset: xxxxxxxx figure 9-25. identi?r register 2 (idr2) ?extended identi?r mapping table 9-28. idr2 register field descriptions ?extended field description 7:0 id[14:7] extended format identi?r the identi?rs consist of 29 bits (id[28:0]) for the extended format. id28 is the most signi?ant bit and is transmitted ?st on the can bus during the arbitration procedure. the priority of an identi?r is de?ed to be highest for the smallest binary number. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 301 9.3.3.1.2 idr0?dr3 for standard identi?r mapping 76543210 r id6 id5 id4 id3 id2 id1 id0 rtr w reset: xxxxxxxx figure 9-26. identi?r register 3 (idr3) ?extended identi?r mapping table 9-29. idr3 register field descriptions ?extended field description 7:1 id[6:0] extended format identi?r the identi?rs consist of 29 bits (id[28:0]) for the extended format. id28 is the most signi?ant bit and is transmitted ?st on the can bus during the arbitration procedure. the priority of an identi?r is de?ed to be highest for the smallest binary number. 0 rtr remote transmission request ?this ?g re?cts the status of the remote transmission request bit in the can frame. in the case of a receive buffer, it indicates the status of the received frame and supports the transmission of an answering frame in software. in the case of a transmit buffer, this ?g de?es the setting of the rtr bit to be sent. 0 data frame 1 remote frame 76543210 r id10 id9 id8 id7 id6 id5 id4 id3 w reset: xxxxxxxx figure 9-27. identi?r register 0 ?standard mapping table 9-30. idr0 register field descriptions ?standard field description 7:0 id[10:3] standard format identi?r the identi?rs consist of 11 bits (id[10:0]) for the standard format. id10 is the most signi?ant bit and is transmitted ?st on the can bus during the arbitration procedure. the priority of an identi?r is de?ed to be highest for the smallest binary number. see also id bits in table 9-31 . 76543210 r id2 id1 id0 rtr ide (=0) w reset: xxxxxxxx = unused; always read ? figure 9-28. identi?r register 1 ?standard mapping chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 302 freescale semiconductor 9.3.3.2 data segment registers (dsr0-7) the eight data segment registers, each with bits db[7:0], contain the data to be transmitted or received. the number of bytes to be transmitted or received is determined by the data length code in the corresponding dlr register. table 9-31. idr1 register field descriptions field description 7:5 id[2:0] standard format identi?r the identi?rs consist of 11 bits (id[10:0]) for the standard format. id10 is the most signi?ant bit and is transmitted ?st on the can bus during the arbitration procedure. the priority of an identi?r is de?ed to be highest for the smallest binary number. see also id bits in table 9-30 . 4 rtr remote transmission request this ?g re?cts the status of the remote transmission request bit in the can frame. in the case of a receive buffer, it indicates the status of the received frame and supports the transmission of an answering frame in software. in the case of a transmit buffer, this ?g de?es the setting of the rtr bit to be sent. 0 data frame 1 remote frame 3 ide id extended this ?g indicates whether the extended or standard identi?r format is applied in this buffer. in the case of a receive buffer, the ?g is set as received and indicates to the cpu how to process the buffer identi?r registers. in the case of a transmit buffer, the ?g indicates to the mscan what type of identi?r to send. 0 standard format (11 bit) 1 extended format (29 bit) 76543210 r w reset: xxxxxxxx = unused; always read ? figure 9-29. identi?r register 2 ?standard mapping 76543210 r w reset: xxxxxxxx = unused; always read ? figure 9-30. identi?r register 3 ?standard mapping chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 303 9.3.3.3 data length register (dlr) this register keeps the data length ?ld of the can frame. module base + 0x0004 (dsr0) 0x0005 (dsr1) 0x0006 (dsr2) 0x0007 (dsr3) 0x0008 (dsr4) 0x0009 (dsr5) 0x000a (dsr6) 0x000b (dsr7) 76543210 r db7 db6 db5 db4 db3 db2 db1 db0 w reset: xxxxxxxx figure 9-31. data segment registers (dsr0?sr7) ?extended identi?r mapping table 9-32. dsr0?sr7 register field descriptions field description 7:0 db[7:0] data bits 7:0 76543210 r dlc3 dlc2 dlc1 dlc0 w reset: xxxxxxxx = unused; always read ? figure 9-32. data length register (dlr) ?extended identi?r mapping table 9-33. dlr register field descriptions field description 3:0 dlc[3:0] data length code bits the data length code contains the number of bytes (data byte count) of the respective message. during the transmission of a remote frame, the data length code is transmitted as programmed while the number of transmitted data bytes is always 0. the data byte count ranges from 0 to 8 for a data frame. table 9-34 shows the effect of setting the dlc bits. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 304 freescale semiconductor 9.3.3.4 transmit buffer priority register (tbpr) this register de?es the local priority of the associated message buffer. the local priority is used for the internal prioritization process of the mscan and is de?ed to be highest for the smallest binary number. the mscan implements the following internal prioritization mechanisms: all transmission buffers with a cleared txex ?g participate in the prioritization immediately before the sof (start of frame) is sent. the transmission buffer with the lowest local priority ?ld wins the prioritization. in cases of more than one buffer having the same lowest priority, the message buffer with the lower index number wins. read: anytime when txex ?g is set (see section 9.3.2.7, ?scan transmitter flag register (cantflg) ? and the corresponding transmit buffer is selected in cantbsel (see section 9.3.2.11, ?scan transmit buffer selection register (cantbsel) ?. write: anytime when txex ?g is set (see section 9.3.2.7, ?scan transmitter flag register (cantflg) ? and the corresponding transmit buffer is selected in cantbsel (see section 9.3.2.11, ?scan transmit buffer selection register (cantbsel) ?. 9.3.3.5 time stamp register (tsrh?srl) if the time bit is enabled, the mscan will write a special time stamp to the respective registers in the active transmit or receive buffer as soon as a message has been acknowledged on the can bus (see table 9-34. data length codes data length code data byte count dlc3 dlc2 dlc1 dlc0 00000 00011 00102 00113 01004 01015 01106 01117 10008 76543210 r prio7 prio6 prio5 prio4 prio3 prio2 prio1 prio0 w reset: 00000000 figure 9-33. transmit buffer priority register (tbpr) chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 305 section 9.3.2.1, ?scan control register 0 (canctl0) ?. the time stamp is written on the bit sample point for the recessive bit of the ack delimiter in the can frame. in case of a transmission, the cpu can only read the time stamp after the respective transmit buffer has been ?gged empty. the timer value, which is used for stamping, is taken from a free running internal can bit clock. a timer overrun is not indicated by the mscan. the timer is reset (all bits set to 0) during initialization mode. the cpu can only read the time stamp registers. read: anytime when txex ?g is set (see section 9.3.2.7, ?scan transmitter flag register (cantflg) ? and the corresponding transmit buffer is selected in cantbsel (see section 9.3.2.11, ?scan transmit buffer selection register (cantbsel) ?. write: unimplemented 9.4 functional description 9.4.1 general this section provides a complete functional description of the mscan. it describes each of the features and modes listed in the introduction. 76543210 r tsr15 tsr14 tsr13 tsr12 tsr11 tsr10 tsr9 tsr8 w reset: xxxxxxxx figure 9-34. time stamp register ?high byte (tsrh) 76543210 r tsr7 tsr6 tsr5 tsr4 tsr3 tsr2 tsr1 tsr0 w reset: xxxxxxxx figure 9-35. time stamp register ?low byte (tsrl) chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 306 freescale semiconductor 9.4.2 message storage figure 9-36. user model for message buffer organization mscan facilitates a sophisticated message storage system which addresses the requirements of a broad range of network applications. mscan rx0 rx1 can receive / transmit engine cpu12 memory mapped i/o cpu bus mscan tx2 txe2 prio receiver transmitter rxbg txbg tx0 txe0 prio txbg tx1 prio txe1 txfg cpu bus rx2 rx3 rx4 rxf rxfg chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 307 9.4.2.1 message transmit background modern application layer software is built upon two fundamental assumptions: any can node is able to send out a stream of scheduled messages without releasing the can bus between the two messages. such nodes arbitrate for the can bus immediately after sending the previous message and only release the can bus in case of lost arbitration. the internal message queue within any can node is organized such that the highest priority message is sent out ?st, if more than one message is ready to be sent. the behavior described in the bullets above cannot be achieved with a single transmit buffer. that buffer must be reloaded immediately after the previous message is sent. this loading process lasts a ?ite amount of time and must be completed within the inter-frame sequence (ifs) to be able to send an uninterrupted stream of messages. even if this is feasible for limited can bus speeds, it requires that the cpu reacts with short latencies to the transmit interrupt. a double buffer scheme de-couples the reloading of the transmit buffer from the actual message sending and, therefore, reduces the reactiveness requirements of the cpu. problems can arise if the sending of a message is ?ished while the cpu re-loads the second buffer. no buffer would then be ready for transmission, and the can bus would be released. at least three transmit buffers are required to meet the ?st of the above requirements under all circumstances. the mscan has three transmit buffers. the second requirement calls for some sort of internal prioritization which the mscan implements with the ?ocal priority?concept described in section 9.4.2.2, ?ransmit structures . 9.4.2.2 transmit structures the mscan triple transmit buffer scheme optimizes real-time performance by allowing multiple messages to be set up in advance. the three buffers are arranged as shown in figure 9-36 . all three buffers have a 13-byte data structure similar to the outline of the receive buffers (see section 9.3.3, ?rogrammer s model of message storage ?. an additional section 9.3.3.4, ?ransmit buffer priority register (tbpr) contains an 8-bit local priority ?ld (prio) (see section 9.3.3.4, ?ransmit buffer priority register (tbpr) ?. the remaining two bytes are used for time stamping of a message, if required (see section 9.3.3.5, ?ime stamp register (tsrh?srl) ?. to transmit a message, the cpu must identify an available transmit buffer, which is indicated by a set transmitter buffer empty (txex) ?g (see section 9.3.2.7, ?scan transmitter flag register (cantflg) ?. if a transmit buffer is available, the cpu must set a pointer to this buffer by writing to the cantbsel register (see section 9.3.2.11, ?scan transmit buffer selection register (cantbsel) ?. this makes the respective buffer accessible within the cantxfg address space (see section 9.3.3, ?rogrammer s model of message storage ?. the algorithmic feature associated with the cantbsel register simpli?s the transmit buffer selection. in addition, this scheme makes the handler software simpler because only one address area is applicable for the transmit process, and the required address space is minimized. the cpu then stores the identi?r, the control bits, and the data content into one of the transmit buffers. finally, the buffer is ?gged as ready for transmission by clearing the associated txe ?g. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 308 freescale semiconductor the mscan then schedules the message for transmission and signals the successful transmission of the buffer by setting the associated txe ?g. a transmit interrupt (see section 9.4.8.2, ?ransmit interrupt ? is generated 1 when txex is set and can be used to drive the application software to re-load the buffer. if more than one buffer is scheduled for transmission when the can bus becomes available for arbitration, the mscan uses the local priority setting of the three buffers to determine the prioritization. for this purpose, every transmit buffer has an 8-bit local priority ?ld (prio). the application software programs this ?ld when the message is set up. the local priority re?cts the priority of this particular message relative to the set of messages being transmitted from this node. the lowest binary value of the prio ?ld is de?ed to be the highest priority. the internal scheduling process takes place whenever the mscan arbitrates for the can bus. this is also the case after the occurrence of a transmission error. when a high priority message is scheduled by the application software, it may become necessary to abort a lower priority message in one of the three transmit buffers. because messages that are already in transmission cannot be aborted, the user must request the abort by setting the corresponding abort request bit (abtrq) (see section 9.3.2.9, ?scan transmitter message abort request register (cantarq) ?) the mscan then grants the request, if possible, by: 1. setting the corresponding abort acknowledge ?g (abtak) in the cantaak register. 2. setting the associated txe ?g to release the buffer. 3. generating a transmit interrupt. the transmit interrupt handler software can determine from the setting of the abtak ?g whether the message was aborted (abtak = 1) or sent (abtak = 0). 9.4.2.3 receive structures the received messages are stored in a ve stage input fifo. the ve message buffers are alternately mapped into a single memory area (see figure 9-36 ). the background receive buffer (rxbg) is exclusively associated with the mscan, but the foreground receive buffer (rxfg) is addressable by the cpu (see figure 9-36 ). this scheme simpli?s the handler software because only one address area is applicable for the receive process. all receive buffers have a size of 15 bytes to store the can control bits, the identi?r (standard or extended), the data contents, and a time stamp, if enabled (see section 9.3.3, ?rogrammer s model of message storage ?. the receiver full ?g (rxf) (see section 9.3.2.5, ?scan receiver flag register (canrflg) ? signals the status of the foreground receive buffer. when the buffer contains a correctly received message with a matching identi?r, this ?g is set. on reception, each message is checked to see whether it passes the ?ter (see section 9.4.3, ?denti?r acceptance filter ? and simultaneously is written into the active rxbg. after successful reception of a valid message, the mscan shifts the content of rxbg into the receiver fifo 2 , sets the rxf ?g, and generates a receive interrupt (see section 9.4.8.3, ?eceive interrupt ? to the cpu 3 . the user s receive handler must read the received message from the rxfg and then reset the rxf ?g to acknowledge the interrupt and to release the foreground buffer. a new message, which can follow immediately after the ifs 1. the transmit interrupt occurs only if not masked. a polling scheme can be applied on txex also. 2. only if the rxf ?g is not set. 3. the receive interrupt occurs only if not masked. a polling scheme can be applied on rxf also. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 309 ?ld of the can frame, is received into the next available rxbg. if the mscan receives an invalid message in its rxbg (wrong identi?r, transmission errors, etc.) the actual contents of the buffer will be over-written by the next message. the buffer will then not be shifted into the fifo. when the mscan module is transmitting, the mscan receives its own transmitted messages into the background receive buffer, rxbg, but does not shift it into the receiver fifo, generate a receive interrupt, or acknowledge its own messages on the can bus. the exception to this rule is in loopback mode (see section 9.3.2.2, ?scan control register 1 (canctl1) ? where the mscan treats its own messages exactly like all other incoming messages. the mscan receives its own transmitted messages in the event that it loses arbitration. if arbitration is lost, the mscan must be prepared to become a receiver. an overrun condition occurs when all receive message buffers in the fifo are ?led with correctly received messages with accepted identi?rs and another message is correctly received from the can bus with an accepted identi?r. the latter message is discarded and an error interrupt with overrun indication is generated if enabled (see section 9.4.8.5, ?rror interrupt ?. the mscan remains able to transmit messages while the receiver fifo being ?led, but all incoming messages are discarded. as soon as a receive buffer in the fifo is available again, new valid messages will be accepted. 9.4.3 identi?r acceptance filter the mscan identi?r acceptance registers (see section 9.3.2.12, ?scan identi?r acceptance control register (canidac) ? de?e the acceptable patterns of the standard or extended identi?r (id[10:0] or id[28:0]). any of these bits can be marked ?on t care?in the mscan identi?r mask registers (see section 9.3.2.17, ?scan identi?r mask registers (canidmr0?anidmr7) ?. a ?ter hit is indicated to the application software by a set receive buffer full ?g (rxf = 1) and three bits in the canidac register (see section 9.3.2.12, ?scan identi?r acceptance control register (canidac) ?. these identi?r hit ?gs (idhit[2:0]) clearly identify the ?ter section that caused the acceptance. they simplify the application software s task to identify the cause of the receiver interrupt. if more than one hit occurs (two or more ?ters match), the lower hit has priority. a very ?xible programmable generic identi?r acceptance ?ter has been introduced to reduce the cpu interrupt loading. the ?ter is programmable to operate in four different modes (see bosch can 2.0a/b protocol speci?ation): two identi?r acceptance ?ters, each to be applied to: the full 29 bits of the extended identi?r and to the following bits of the can 2.0b frame: remote transmission request (rtr) identi?r extension (ide) substitute remote request (srr) the 11 bits of the standard identi?r plus the rtr and ide bits of the can 2.0a/b messages 1 . this mode implements two ?ters for a full length can 2.0b compliant extended identi?r. figure 9-37 shows how the ?st 32-bit ?ter bank (canidar0?anidar3, canidmr0?anidmr3) produces a ?ter 0 hit. similarly, the second ?ter bank (canidar4?anidar7, canidmr4?anidmr7) produces a ?ter 1 hit. 1.although this mode can be used for standard identifiers, it is recommended to use the four or eight identifier acceptance filters for standard identifiers chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 310 freescale semiconductor four identi?r acceptance ?ters, each to be applied to a) the 14 most signi?ant bits of the extended identi?r plus the srr and ide bits of can 2.0b messages or b) the 11 bits of the standard identi?r, the rtr and ide bits of can 2.0a/b messages. figure 9-38 shows how the ?st 32-bit ?ter bank (canidar0?anida3, canidmr0?canidmr) produces ?ter 0 and 1 hits. similarly, the second ?ter bank (canidar4?anidar7, canidmr4?anidmr7) produces ?ter 2 and 3 hits. eight identi?r acceptance ?ters, each to be applied to the ?st 8 bits of the identi?r. this mode implements eight independent ?ters for the ?st 8 bits of a can 2.0a/b compliant standard identi?r or a can 2.0b compliant extended identi?r. figure 9-39 shows how the ?st 32-bit ?ter bank (canidar0?anidar3, canidmr0?anidmr3) produces ?ter 0 to 3 hits. similarly, the second ?ter bank (canidar4?anidar7, canidmr4?anidmr7) produces ?ter 4 to 7 hits. closed ?ter. no can message is copied into the foreground buffer rxfg, and the rxf ?g is never set. figure 9-37. 32-bit maskable identi?r acceptance filter id28 id21 idr0 id10 id3 idr0 id20 id15 idr1 id2 ide idr1 id14 id7 idr2 id10 id3 idr2 id6 rtr idr3 id10 id3 idr3 ac7 ac0 canidar0 am7 am0 canidmr0 ac7 ac0 canidar1 am7 am0 canidmr1 ac7 ac0 canidar2 am7 am0 canidmr2 ac7 ac0 canidar3 am7 am0 canidmr3 id accepted (filter 0 hit) can 2.0b extended identi?r can 2.0a/b standard identi?r chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 311 figure 9-38. 16-bit maskable identi?r acceptance filters id28 id21 idr0 id10 id3 idr0 id20 id15 idr1 id2 ide idr1 id14 id7 idr2 id10 id3 idr2 id6 rtr idr3 id10 id3 idr3 ac7 ac0 canidar0 am7 am0 canidmr0 ac7 ac0 canidar1 am7 am0 canidmr1 id accepted (filter 0 hit) ac7 ac0 canidar2 am7 am0 canidmr2 ac7 ac0 canidar3 am7 am0 canidmr3 id accepted (filter 1 hit) can 2.0b extended identi?r can 2.0a/b standard identi?r chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 312 freescale semiconductor figure 9-39. 8-bit maskable identi?r acceptance filters can 2.0b extended identi?r can 2.0a/b standard identi?r ac7 ac0 cidar3 am7 am0 cidmr3 id accepted (filter 3 hit) ac7 ac0 cidar2 am7 am0 cidmr2 id accepted (filter 2 hit) ac7 ac0 cidar1 am7 am0 cidmr1 id accepted (filter 1 hit) id28 id21 idr0 id10 id3 idr0 id20 id15 idr1 id2 ide idr1 id14 id7 idr2 id10 id3 idr2 id6 rtr idr3 id10 id3 idr3 ac7 ac0 cidar0 am7 am0 cidmr0 id accepted (filter 0 hit) chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 313 9.4.3.1 protocol violation protection the mscan protects the user from accidentally violating the can protocol through programming errors. the protection logic implements the following features: the receive and transmit error counters cannot be written or otherwise manipulated. all registers which control the con?uration of the mscan cannot be modi?d while the mscan is on-line. the mscan has to be in initialization mode. the corresponding initrq/initak handshake bits in the canctl0/canctl1 registers (see section 9.3.2.1, ?scan control register 0 (canctl0) ? serve as a lock to protect the following registers: mscan control 1 register (canctl1) mscan bus timing registers 0 and 1 (canbtr0, canbtr1) mscan identi?r acceptance control register (canidac) mscan identi?r acceptance registers (canidar0?anidar7) mscan identi?r mask registers (canidmr0?anidmr7) the txcan pin is immediately forced to a recessive state when the mscan goes into the power down mode or initialization mode (see section 9.4.6.6, ?scan power down mode , and section 9.4.6.5, ?scan initialization mode ?. the mscan enable bit (cane) is writable only once in normal system operation modes, which provides further protection against inadvertently disabling the mscan. 9.4.3.2 clock system figure 9-40 shows the structure of the mscan clock generation circuitry. figure 9-40. mscan clocking scheme the clock source bit (clksrc) in the canctl1 register ( 9.3.2.2/9-278 ) de?es whether the internal canclk is connected to the output of a crystal oscillator (oscillator clock) or to the bus clock. the clock source has to be chosen such that the tight oscillator tolerance requirements (up to 0.4%) of the can protocol are met. additionally, for high can bus rates (1 mbps), a 45% to 55% duty cycle of the clock is required. bus clock oscillator clock mscan canclk clksrc clksrc prescaler (1 .. 64) time quanta clock (tq) chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 314 freescale semiconductor if the bus clock is generated from a pll, it is recommended to select the oscillator clock rather than the bus clock due to jitter considerations, especially at the faster can bus rates. for microcontrollers without a clock and reset generator (crg), canclk is driven from the crystal oscillator (oscillator clock). a programmable prescaler generates the time quanta (tq) clock from canclk. a time quantum is the atomic unit of time handled by the mscan. eqn. 9-2 a bit time is subdivided into three segments as described in the bosch can speci?ation. (see figure 9-41 ): sync_seg: this segment has a ?ed length of one time quantum. signal edges are expected to happen within this section. time segment 1: this segment includes the prop_seg and the phase_seg1 of the can standard. it can be programmed by setting the parameter tseg1 to consist of 4 to 16 time quanta. time segment 2: this segment represents the phase_seg2 of the can standard. it can be programmed by setting the tseg2 parameter to be 2 to 8 time quanta long. eqn. 9-3 figure 9-41. segments within the bit time tq f canclk prescaler value ( ) ---------------------------------------------------- -- = bit rate f tq number of time quanta () -------------------------------------------------------------------------------- - = sync_seg time segment 1 time segment 2 1 4 ... 16 2 ... 8 8 ... 25 time quanta = 1 bit time nrz signal sample point (single or triple sampling) (prop_seg + phase_seg1) (phase_seg2) transmit point chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 315 the synchronization jump width (see the bosch can speci?ation for details) can be programmed in a range of 1 to 4 time quanta by setting the sjw parameter. the sync_seg, tseg1, tseg2, and sjw parameters are set by programming the mscan bus timing registers (canbtr0, canbtr1) (see section 9.3.2.3, ?scan bus timing register 0 (canbtr0) and section 9.3.2.4, ?scan bus timing register 1 (canbtr1) ?. table 9-36 gives an overview of the can compliant segment settings and the related parameter values. note it is the user s responsibility to ensure the bit time settings are in compliance with the can standard. 9.4.4 timer link the mscan generates an internal time stamp whenever a valid frame is received or transmitted and the time bit is enabled. because the can speci?ation de?es a frame to be valid if no errors occur before the end of frame (eof) ?ld is transmitted successfully, the actual value of an internal timer is written at eof to the appropriate time stamp position within the transmit buffer. for receive frames, the time stamp is written to the receive buffer. table 9-35. time segment syntax syntax description sync_seg system expects transitions to occur on the can bus during this period. transmit point a node in transmit mode transfers a new value to the can bus at this point. sample point a node in receive mode samples the can bus at this point. if the three samples per bit option is selected, then this point marks the position of the third sample. table 9-36. can standard compliant bit time segment settings time segment 1 tseg1 time segment 2 tseg2 synchronization jump width sjw 5 .. 10 4 .. 9 2 1 1 .. 2 0 .. 1 4 .. 11 3 .. 10 3 2 1 .. 3 0 .. 2 5 .. 12 4 .. 11 4 3 1 .. 4 0 .. 3 6 .. 13 5 .. 12 5 4 1 .. 4 0 .. 3 7 .. 14 6 .. 13 6 5 1 .. 4 0 .. 3 8 .. 15 7 .. 14 7 6 1 .. 4 0 .. 3 9 .. 16 8 .. 15 8 7 1 .. 4 0 .. 3 chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 316 freescale semiconductor 9.4.5 modes of operation 9.4.5.1 normal modes the mscan module behaves as described within this speci?ation in all normal system operation modes. 9.4.5.2 special modes the mscan module behaves as described within this speci?ation in all special system operation modes. 9.4.5.3 emulation modes in all emulation modes, the mscan module behaves just like normal system operation modes as described within this speci?ation. 9.4.5.4 listen-only mode in an optional can bus monitoring mode (listen-only), the can node is able to receive valid data frames and valid remote frames, but it sends only ?ecessive?bits on the can bus. in addition, it cannot start a transmision. if the mac sub-layer is required to send a ?ominant bit (ack bit, overload ?g, or active error ?g), the bit is rerouted internally so that the mac sub-layer monitors this ?ominant bit, although the can bus may remain in recessive state externally. 9.4.5.5 security modes the mscan module has no security features. 9.4.6 low-power options if the mscan is disabled (cane = 0), the mscan clocks are stopped for power saving. if the mscan is enabled (cane = 1), the mscan has two additional modes with reduced power consumption, compared to normal mode: sleep and power down mode. in sleep mode, power consumption is reduced by stopping all clocks except those to access the registers from the cpu side. in power down mode, all clocks are stopped and no power is consumed. table 9-37 summarizes the combinations of mscan and cpu modes. a particular combination of modes is entered by the given settings on the cswai and slprq/slpak bits. for all modes, an mscan wake-up interrupt can occur only if the mscan is in sleep mode (slprq = 1 and slpak = 1), wake-up functionality is enabled (wupe = 1), and the wake-up interrupt is enabled (wupie = 1). chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 317 9.4.6.1 operation in run mode as shown in table 9-37 , only mscan sleep mode is available as low power option when the cpu is in run mode. 9.4.6.2 operation in wait mode the wai instruction puts the mcu in a low power consumption stand-by mode. if the cswai bit is set, additional power can be saved in power down mode because the cpu clocks are stopped. after leaving this power down mode, the mscan restarts its internal controllers and enters normal mode again. while the cpu is in wait mode, the mscan can be operated in normal mode and generate interrupts (registers can be accessed via background debug mode). the mscan can also operate in any of the low-power modes depending on the values of the slprq/slpak and cswai bits as seen in table 9-37 . 9.4.6.3 operation in stop mode the stop instruction puts the mcu in a low power consumption stand-by mode. in stop mode, the mscan is set in power down mode regardless of the value of the slprq/slpak and cswai bits table 9-37 . 9.4.6.4 mscan sleep mode the cpu can request the mscan to enter this low power mode by asserting the slprq bit in the canctl0 register. the time when the mscan enters sleep mode depends on a ?ed synchronization delay and its current activity: table 9-37. cpu vs. mscan operating modes cpu mode mscan mode normal reduced power consumption sleep power down disabled (cane=0) run cswai = x 1 slprq = 0 slpak = 0 1 ??means don? care. cswai = x slprq = 1 slpak = 1 cswai = x slprq = x slpak = x wait cswai = 0 slprq = 0 slpak = 0 cswai = 0 slprq = 1 slpak = 1 cswai = 1 slprq = x slpak = x cswai = x slprq = x slpak = x stop cswai = x slprq = x slpak = x cswai = x slprq = x slpak = x chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 318 freescale semiconductor if there are one or more message buffers scheduled for transmission (txex = 0), the mscan will continue to transmit until all transmit message buffers are empty (txex = 1, transmitted successfully or aborted) and then goes into sleep mode. if the mscan is receiving, it continues to receive and goes into sleep mode as soon as the can bus next becomes idle. if the mscan is neither transmitting nor receiving, it immediately goes into sleep mode. figure 9-42. sleep request / acknowledge cycle note the application software must avoid setting up a transmission (by clearing one or more txex ?g(s)) and immediately request sleep mode (by setting slprq). whether the mscan starts transmitting or goes into sleep mode directly depends on the exact sequence of operations. if sleep mode is active, the slprq and slpak bits are set ( figure 9-42 ). the application software must use slpak as a handshake indication for the request (slprq) to go into sleep mode. when in sleep mode (slprq = 1 and slpak = 1), the mscan stops its internal clocks. however, clocks that allow register accesses from the cpu side continue to run. if the mscan is in bus-off state, it stops counting the 128 occurrences of 11 consecutive recessive bits due to the stopped clocks. the txcan pin remains in a recessive state. if rxf = 1, the message can be read and rxf can be cleared. shifting a new message into the foreground buffer of the receiver fifo (rxfg) does not take place while in sleep mode. it is possible to access the transmit buffers and to clear the associated txe ?gs. no message abort takes place while in sleep mode. if the wupe bit in canclt0 is not asserted, the mscan will mask any activity it detects on can. the rxcan pin is therefore held internally in a recessive state. this locks the mscan in sleep mode ( figure 9-43 ). sync sync bus cloc k domain can cloc k domain mscan in sleep mode cpu sleep request slprq flag slpak flag slprq sync. slpak sync. slprq slpak chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 319 the mscan is able to leave sleep mode (wake up) only when: can bus activity occurs and wupe = 1 or the cpu clears the slprq bit note the cpu cannot clear the slprq bit before sleep mode (slprq = 1 and slpak = 1) is active. after wake-up, the mscan waits for 11 consecutive recessive bits to synchronize to the can bus. as a consequence, if the mscan is woken-up by a can frame, this frame is not received. the receive message buffers (rxfg and rxbg) contain messages if they were received before sleep mode was entered. all pending actions will be executed upon wake-up; copying of rxbg into rxfg, message aborts and message transmissions. if the mscan remains in bus-off state after sleep mode was exited, it continues counting the 128 occurrences of 11 consecutive recessive bits. figure 9-43. simpli?d state transitions for entering/leaving sleep mode wait idle tx/rx message active can activity can activity & sleep slprq startup for idle (can activity & wupe) | (can activity & wupe) | slprq can activity can activity can activity & can activity slprq slprq can activity chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 320 freescale semiconductor 9.4.6.5 mscan initialization mode in initialization mode, any on-going transmission or reception is immediately aborted and synchronization to the can bus is lost, potentially causing can protocol violations. to protect the can bus system from fatal consequences of violations, the mscan immediately drives the txcan pin into a recessive state. note the user is responsible for ensuring that the mscan is not active when initialization mode is entered. the recommended procedure is to bring the mscan into sleep mode (slprq = 1 and slpak = 1) before setting the initrq bit in the canctl0 register. otherwise, the abort of an on-going message can cause an error condition and can impact other can bus devices. in initialization mode, the mscan is stopped. however, interface registers remain accessible. this mode is used to reset the canctl0, canrflg, canrier, cantflg, cantier, cantarq, cantaak, and cantbsel registers to their default values. in addition, the mscan enables the con?uration of the canbtr0, canbtr1 bit timing registers; canidac; and the canidar, canidmr message ?ters. see section 9.3.2.1, ?scan control register 0 (canctl0) , for a detailed description of the initialization mode. figure 9-44. initialization request/acknowledge cycle due to independent clock domains within the mscan, initrq must be synchronized to all domains by using a special handshake mechanism. this handshake causes additional synchronization delay (see section figure 9-44., ?nitialization request/acknowledge cycle ?. if there is no message transfer ongoing on the can bus, the minimum delay will be two additional bus clocks and three additional can clocks. when all parts of the mscan are in initialization mode, the initak ?g is set. the application software must use initak as a handshake indication for the request (initrq) to go into initialization mode. note the cpu cannot clear initrq before initialization mode (initrq = 1 and initak = 1) is active. sync sync bus cloc k domain can cloc k domain cpu init request init flag initak flag initrq sync. initak sync. initrq initak chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 321 9.4.6.6 mscan power down mode the mscan is in power down mode ( table 9-37 ) when cpu is in stop mode or cpu is in wait mode and the cswai bit is set when entering the power down mode, the mscan immediately stops all ongoing transmissions and receptions, potentially causing can protocol violations. to protect the can bus system from fatal consequences of violations to the above rule, the mscan immediately drives the txcan pin into a recessive state. note the user is responsible for ensuring that the mscan is not active when power down mode is entered. the recommended procedure is to bring the mscan into sleep mode before the stop or wai instruction (if cswai is set) is executed. otherwise, the abort of an ongoing message can cause an error condition and impact other can bus devices. in power down mode, all clocks are stopped and no registers can be accessed. if the mscan was not in sleep mode before power down mode became active, the module performs an internal recovery cycle after powering up. this causes some ?ed delay before the module enters normal mode again. 9.4.6.7 programmable wake-up function the mscan can be programmed to wake up the mscan as soon as can bus activity is detected (see control bit wupe in section 9.3.2.1, ?scan control register 0 (canctl0) ?. the sensitivity to existing can bus action can be modi?d by applying a low-pass ?ter function to the rxcan input line while in sleep mode (see control bit wupm in section 9.3.2.2, ?scan control register 1 (canctl1) ?. this feature can be used to protect the mscan from wake-up due to short glitches on the can bus lines. such glitches can result from?or example?lectromagnetic interference within noisy environments. 9.4.7 reset initialization the reset state of each individual bit is listed in section 9.3.2, ?egister descriptions , which details all the registers and their bit-?lds. 9.4.8 interrupts this section describes all interrupts originated by the mscan. it documents the enable bits and generated ?gs. each interrupt is listed and described separately. chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 322 freescale semiconductor 9.4.8.1 description of interrupt operation the mscan supports four interrupt vectors (see table 9-38 ), any of which can be individually masked (for details see sections from section 9.3.2.6, ?scan receiver interrupt enable register (canrier) , to section 9.3.2.8, ?scan transmitter interrupt enable register (cantier) ?. note the dedicated interrupt vector addresses are de?ed in the resets and interrupts chapter. 9.4.8.2 transmit interrupt at least one of the three transmit buffers is empty (not scheduled) and can be loaded to schedule a message for transmission. the txex ?g of the empty message buffer is set. 9.4.8.3 receive interrupt a message is successfully received and shifted into the foreground buffer (rxfg) of the receiver fifo. this interrupt is generated immediately after receiving the eof symbol. the rxf ?g is set. if there are multiple messages in the receiver fifo, the rxf ?g is set as soon as the next message is shifted to the foreground buffer. 9.4.8.4 wake-up interrupt a wake-up interrupt is generated if activity on the can bus occurs during mscn internal sleep mode. wupe (see section 9.3.2.1, ?scan control register 0 (canctl0) ? must be enabled. 9.4.8.5 error interrupt an error interrupt is generated if an overrun of the receiver fifo, error, warning, or bus-off condition occurrs. section 9.3.2.5, ?scan receiver flag register (canrflg) indicates one of the following conditions: overrun an overrun condition of the receiver fifo as described in section 9.4.2.3, ?eceive structures , occurred. can status change ?the actual value of the transmit and receive error counters control the can bus state of the mscan. as soon as the error counters skip into a critical range (tx/rx-warning, tx/rx-error, bus-off) the mscan ?gs an error condition. the status change, which caused the error condition, is indicated by the tstat and rstat ?gs (see section 9.3.2.5, table 9-38. interrupt vectors interrupt source ccr mask local enable wake-up interrupt (wupif) i bit canrier (wupie) error interrupts interrupt (cscif, ovrif) i bit canrier (cscie, ovrie) receive interrupt (rxf) i bit canrier (rxfie) transmit interrupts (txe[2:0]) i bit cantier (txeie[2:0]) chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 323 ?scan receiver flag register (canrflg) and section 9.3.2.6, ?scan receiver interrupt enable register (canrier) ?. 9.4.8.6 interrupt acknowledge interrupts are directly associated with one or more status ?gs in either the section 9.3.2.5, ?scan receiver flag register (canrflg) ?or the section 9.3.2.7, ?scan transmitter flag register (cantflg) . interrupts are pending as long as one of the corresponding ?gs is set. the ?gs in canrflg and cantflg must be reset within the interrupt handler to handshake the interrupt. the ?gs are reset by writing a 1 to the corresponding bit position. a ?g cannot be cleared if the respective condition prevails. note it must be guaranteed that the cpu clears only the bit causing the current interrupt. for this reason, bit manipulation instructions (bset) must not be used to clear interrupt ?gs. these instructions may cause accidental clearing of interrupt ?gs which are set after entering the current interrupt service routine. 9.4.8.7 recovery from stop or wait the mscan can recover from stop or wait via the wake-up interrupt. this interrupt can only occur if the mscan was in sleep mode (slprq = 1 and slpak = 1) before entering power down mode, the wake-up option is enabled (wupe = 1), and the wake-up interrupt is enabled (wupie = 1). 9.5 initialization/application information 9.5.1 mscan initialization the procedure to initially start up the mscan module out of reset is as follows: 1. assert cane 2. write to the con?uration registers in initialization mode 3. clear initrq to leave initialization mode and enter normal mode if the con?uration of registers which are writable in initialization mode needs to be changed only when the mscan module is in normal mode: 1. bring the module into sleep mode by setting slprq and awaiting slpak to assert after the can bus becomes idle. 2. enter initialization mode: assert initrq and await initak 3. write to the con?uration registers in initialization mode 4. clear initrq to leave initialization mode and continue in normal mode chapter 9 freescale s scalable controller area network (mscanv2) mc9s12kg128 data sheet, rev. 1.15 324 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 325 chapter 10 serial communications interface (sciv1) 10.1 introduction this block guide provide an overview of serial communication interface (sci) module. the sci allows asynchronous serial communications with peripheral devices and other cpus. 10.1.1 glossary irq ?interrupt request lsb ?least signi?ant bit msb ?most signi?ant bit nrz ?non-return-to-zero rzi ?return-to-zero-inverted rxd ?receive pin sci ?serial communication interface txd ?transmit pin 10.1.2 features the sci includes these distinctive features: full-duplex operation standard mark/space non-return-to-zero (nrz) format 13-bit baud rate selection programmable 8-bit or 9-bit data format separately enabled transmitter and receiver programmable transmitter output parity two receiver wake up methods: idle line wake-up address mark wake-up interrupt-driven operation with eight ?gs: transmitter empty transmission complete chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 326 freescale semiconductor receiver full idle receiver input receiver overrun noise error framing error parity error receiver framing error detection hardware parity checking 1/16 bit-time noise detection 10.1.3 modes of operation the sci operation is the same independent of device resource mapping and bus interface mode. different power modes are available to facilitate power saving. 10.1.3.1 run mode normal mode of operation. 10.1.3.2 wait mode sci operation in wait mode depends on the state of the sciswai bit in the sci control register 1 (scicr1). if sciswai is clear, the sci operates normally when the cpu is in wait mode. if sciswai is set, sci clock generation ceases and the sci module enters a power-conservation state when the cpu is in wait mode. setting sciswai does not affect the state of the receiver enable bit, re, or the transmitter enable bit, te. if sciswai is set, any transmission or reception in progress stops at wait mode entry. the transmission or reception resumes when either an internal or external interrupt brings the cpu out of wait mode. exiting wait mode by reset aborts any transmission or reception in progress and resets the sci. 10.1.3.3 stop mode the sci is inactive during stop mode for reduced power consumption. the stop instruction does not affect the sci register states, but the sci module clock will be disabled. the sci operation resumes from where it left off after an external interrupt brings the cpu out of stop mode. exiting stop mode by reset aborts any transmission or reception in progress and resets the sci. 10.1.4 block diagram figure 10-1 is a high level block diagram of the sci module, showing the interaction of various functional blocks. chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 327 figure 10-1. sci block diagram 10.2 external signal description the sci module has a total of two external pins: 10.2.1 txd-sci transmit pin this pin serves as transmit data output of sci. 10.2.2 rxd-sci receive pin this pin serves as receive data input of the sci. sci data register receive shift register receive & wake up control data format control transmit control transmit shift register sci data register baud generator rx data in 16 bus clock txdata out idle irq rdr/or irq tdre irq tc irq oring irq generation irq generation irq to cpu chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 328 freescale semiconductor 10.3 memory map and registers this section provides a detailed description of all memory and registers. 10.3.1 module memory map the memory map for the sci module is given below in figure 10-2 . the address listed for each register is the address offset. the total address for each register is the sum of the base address for the sci module and the address offset for each register. 10.3.2 register descriptions this section consists of register descriptions in address order. each description includes a standard register diagram with an associated ?ure number. writes to a reserved register location do not have any effect and reads of these locations return a zero. details of register bit and ?ld function follow the register diagrams, in bit order. address name bit 7 65432 1 bit 0 0x0000 scibdh r0 0 0 sbr12 sbr11 sbr10 sbr9 sbr8 w 0x0001 scibdl r sbr7 sbr6 sbr5 sbr4 sbr3 sbr2 sbr1 sbr0 w 0x0002 scicr1 r loops sciswai rsrc m wake ilt pe pt w 0x0003 scicr2 r tie tcie rie ilie te re rwu sbk w 0x0004 scisr1 r tdre tc rdrf idle or nf fe pf w 0x0005 scisr2 r0 0000 brk13 txdir raf w 0x0006 scidrh rr8 t8 0000 0 0 w 0x0007 scidrl rr7 r6r5r4r3r2 r1 r0 wt7 t6t5t4t3t2 t1 t0 = unimplemented or reserved figure 10-2. sci register summary chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 329 10.3.2.1 sci baud rate registers (scibdh and schbdl) the sci baud rate register is used by the counter to determine the baud rate of the sci. the formula for calculating the baud rate is: sci baud rate = sci module clock / (16 x br) where: br is the content of the sci baud rate registers, bits sbr12 through sbr0. the baud rate registers can contain a value from 1 to 8191. read: anytime. if only scibdh is written to, a read will not return the correct data until scibdl is written to as well, following a write to scibdh. write: anytime module base + 0x_0000 76543210 r000 sbr12 sbr11 sbr10 sbr9 sbr8 w reset 0 0 0 00000 module base + 0x_0001 76543210 r sbr7 sbr6 sbr5 sbr4 sbr3 sbr2 sbr1 sbr0 w reset 0 0 0 00100 = unimplemented or reserved figure 10-3. sci baud rate registers (scibdh and scibdl) table 10-1. scibdh and scibdl field descriptions field description 4? 7? sbr[12:0] sci baud rate bits ?the baud rate for the sci is determined by these 13 bits. note: the baud rate generator is disabled until the te bit or the re bit is set for the ?st time after reset. the baud rate generator is disabled when br = 0. writing to scibdh has no effect without writing to scibdl, since writing to scibdh puts the data in a temporary location until scibdl is written to. chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 330 freescale semiconductor 10.3.2.2 sci control register 1 (scicr1) read: anytime write: anytime module base + 0x_0002 76543210 r loops sciswai rsrc m wake ilt pe pt w reset 0 0 0 00000 figure 10-4. sci control register 1 (scicr1) table 10-2. scicr1 field descriptions field description 7 loops loop select bit loops enables loop operation. in loop operation, the rxd pin is disconnected from the sci and the transmitter output is internally connected to the receiver input. both the transmitter and the receiver must be enabled to use the loop function.see table 10-3 . 0 normal operation enabled 1 loop operation enabled note: the receiver input is determined by the rsrc bit. 6 sciswai sci stop in wait mode bit ?sciswai disables the sci in wait mode. 0 sci enabled in wait mode 1 sci disabled in wait mode 5 rsrc receiver source bit ?when loops = 1, the rsrc bit determines the source for the receiver shift register input. 0 receiver input internally connected to transmitter output 1 receiver input connected externally to transmitter 4 m data format mode bit ?mode determines whether data characters are eight or nine bits long. 0 one start bit, eight data bits, one stop bit 1 one start bit, nine data bits, one stop bit 3 wake wakeup condition bit wake determines which condition wakes up the sci: a logic 1 (address mark) in the most signi?ant bit position of a received data character or an idle condition on the rxd. 0 idle line wakeup 1 address mark wakeup 2 ilt idle line type bit ?ilt determines when the receiver starts counting logic 1s as idle character bits. the counting begins either after the start bit or after the stop bit. if the count begins after the start bit, then a string of logic 1s preceding the stop bit may cause false recognition of an idle character. beginning the count after the stop bit avoids false idle character recognition, but requires properly synchronized transmissions. 0 idle character bit count begins after start bit 1 idle character bit count begins after stop bit 1 pe parity enable bit pe enables the parity function. when enabled, the parity function inserts a parity bit in the most signi?ant bit position. 0 parity function disabled 1 parity function enabled 0 pt parity type bit pt determines whether the sci generates and checks for even parity or odd parity. with even parity, an even number of 1s clears the parity bit and an odd number of 1s sets the parity bit. with odd parity, an odd number of 1s clears the parity bit and an even number of 1s sets the parity bit. 0 even parity 1 odd parity chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 331 10.3.2.3 sci control register 2 (scicr2) read: anytime write: anytime table 10-3. loop functions loops rsrc function 0 x normal operation 1 0 loop mode with rx input internally connected to tx output 1 1 single-wire mode with rx input connected to txd module base + 0x_0003 76543210 r tie tcie rie ilie te re rwu sbk w reset 0 0 0 00000 figure 10-5. sci control register 2 (scicr2) table 10-4. scicr2 field descriptions field description 7 tie transmitter interrupt enable bit ?tie enables the transmit data register empty ?g, tdre, to generate interrupt requests. 0 tdre interrupt requests disabled 1 tdre interrupt requests enabled 6 tcie transmission complete interrupt enable bit tcie enables the transmission complete ?g, tc, to generate interrupt requests. 0 tc interrupt requests disabled 1 tc interrupt requests enabled 5 rie receiver full interrupt enable bit rie enables the receive data register full ?g, rdrf, or the overrun ?g, or, to generate interrupt requests. 0 rdrf and or interrupt requests disabled 1 rdrf and or interrupt requests enabled 4 ilie idle line interrupt enable bit ?ilie enables the idle line ?g, idle, to generate interrupt requests. 0 idle interrupt requests disabled 1 idle interrupt requests enabled 3 te transmitter enable bit ?te enables the sci transmitter and con?ures the txd pin as being controlled by the sci. the te bit can be used to queue an idle preamble. 0 transmitter disabled 1 transmitter enabled 2 re receiver enable bit ?re enables the sci receiver. 0 receiver disabled 1 receiver enabled chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 332 freescale semiconductor 10.3.2.4 sci status register 1 (scisr1) the scisr1 and scisr2 registers provides inputs to the mcu for generation of sci interrupts. also, these registers can be polled by the mcu to check the status of these bits. the ?g-clearing procedures require that the status register be read followed by a read or write to the sci data register.it is permissible to execute other instructions between the two steps as long as it does not compromise the handling of i/o, but the order of operations is important for ?g clearing. read: anytime write: has no meaning or effect 1 rwu receiver wakeup bit ?standby state 0 normal operation. 1 rwu enables the wakeup function and inhibits further receiver interrupt requests. normally, hardware wakes the receiver by automatically clearing rwu. 0 sbk send break bit ?toggling sbk sends one break character (10 or 11 logic 0s, respectively 13 or 14 logics 0s if brk13 is set). toggling implies clearing the sbk bit before the break character has ?ished transmitting. as long as sbk is set, the transmitter continues to send complete break characters (10 or 11 bits, respectively 13 or 14 bits). 0 no break characters 1 transmit break characters module base + 0x_0004 76543210 r tdre tc rdrf idle or nf fe pf w reset 0 0 0 00000 = unimplemented or reserved figure 10-6. sci status register 1 (scisr1) table 10-5. scisr1 field descriptions field description 7 tdre transmit data register empty flag ?tdre is set when the transmit shift register receives a byte from the sci data register. when tdre is 1, the transmit data register (scidrh/l) is empty and can receive a new value to transmit.clear tdre by reading sci status register 1 (scisr1), with tdre set and then writing to sci data register low (scidrl). 0 no byte transferred to transmit shift register 1 byte transferred to transmit shift register; transmit data register empty 6 tc transmit complete flag tc is set low when there is a transmission in progress or when a preamble or break character is loaded. tc is set high when the tdre ?g is set and no data, preamble, or break character is being transmitted.when tc is set, the txd out signal becomes idle (logic 1). clear tc by reading sci status register 1 (scisr1) with tc set and then writing to sci data register low (scidrl). tc is cleared automatically when data, preamble, or break is queued and ready to be sent. tc is cleared in the event of a simultaneous set and clear of the tc ?g (transmission not complete). 0 transmission in progress 1 no transmission in progress table 10-4. scicr2 field descriptions (continued) field description chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 333 5 rdrf receive data register full flag rdrf is set when the data in the receive shift register transfers to the sci data register. clear rdrf by reading sci status register 1 (scisr1) with rdrf set and then reading sci data register low (scidrl). 0 data not available in sci data register 1 received data available in sci data register 4 idle idle line flag ?idle is set when 10 consecutive logic 1s (if m=0) or 11 consecutive logic 1s (if m=1) appear on the receiver input. once the idle ?g is cleared, a valid frame must again set the rdrf ?g before an idle condition can set the idle ?g.clear idle by reading sci status register 1 (scisr1) with idle set and then reading sci data register low (scidrl). 0 receiver input is either active now or has never become active since the idle ?g was last cleared 1 receiver input has become idle note: when the receiver wakeup bit (rwu) is set, an idle line condition does not set the idle ?g. 3 or overrun flag ?or is set when software fails to read the sci data register before the receive shift register receives the next frame. the or bit is set immediately after the stop bit has been completely received for the second frame. the data in the shift register is lost, but the data already in the sci data registers is not affected. clear or by reading sci status register 1 (scisr1) with or set and then reading sci data register low (scidrl). 0 no overrun 1 overrun note: or ?g may read back as set when rdrf ?g is clear. this may happen if the following sequence of events occurs: 1. after the ?st frame is received, read status register scisr1 (returns rdrf set and or ?g clear); 2. receive second frame without reading the ?st frame in the data register (the second frame is not received and or ?g is set); 3. read data register scidrl (returns ?st frame and clears rdrf ?g in the status register); 4. read status register scisr1 (returns rdrf clear and or set). event 3 may be at exactly the same time as event 2 or any time after. when this happens, a dummy scidrl read following event 4 will be required to clear the or ?g if further frames are to be received. 2 nf noise flag nf is set when the sci detects noise on the receiver input. nf bit is set during the same cycle as the rdrf ?g but does not get set in the case of an overrun. clear nf by reading sci status register 1(scisr1), and then reading sci data register low (scidrl). 0 no noise 1 noise 1 fe framing error flag fe is set when a logic 0 is accepted as the stop bit. fe bit is set during the same cycle as the rdrf ?g but does not get set in the case of an overrun. fe inhibits further data reception until it is cleared. clear fe by reading sci status register 1 (scisr1) with fe set and then reading the sci data register low (scidrl). 0 no framing error 1 framing error 0 pf parity error flag pf is set when the parity enable bit (pe) is set and the parity of the received data does not match the parity type bit (pt). pf bit is set during the same cycle as the rdrf ?g but does not get set in the case of an overrun. clear pf by reading sci status register 1 (scisr1), and then reading sci data register low (scidrl). 0 no parity error 1 parity error table 10-5. scisr1 field descriptions (continued) field description chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 334 freescale semiconductor 10.3.2.5 sci status register 2 (scisr2) read: anytime write: anytime; writing accesses sci status register 2; writing to any bits except txdir and brk13 (scisr2[1] & [2]) has no effect module base + 0x_0005 76543210 r00000 bk13 txdir raf w reset 0 0 0 00000 = unimplemented or reserved figure 10-7. sci status register 2 (scisr2) table 10-6. scisr2 field descriptions field description 2 bk13 break transmit character length ?this bit determines whether the transmit break character is 10 or 11 bit respectively 13 or 14 bits long. the detection of a framing error is not affected by this bit. 0 break character is 10 or 11 bit long 1 break character is 13 or 14 bit long 1 txdir transmitter pin data direction in single-wire mode. this bit determines whether the txd pin is going to be used as an input or output, in the single-wire mode of operation. this bit is only relevant in the single-wire mode of operation. 0 txd pin to be used as an input in single-wire mode 1 txd pin to be used as an output in single-wire mode 0 raf receiver active flag raf is set when the receiver detects a logic 0 during the rt1 time period of the start bit search. raf is cleared when the receiver detects an idle character. 0 no reception in progress 1 reception in progress chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 335 10.3.2.6 sci data registers (scidrh and scidrl) read: anytime; reading accesses sci receive data register write: anytime; writing accesses sci transmit data register; writing to r8 has no effect note if the value of t8 is the same as in the previous transmission, t8 does not have to be rewritten.the same value is transmitted until t8 is rewritten in 8-bit data format, only sci data register low (scidrl) needs to be accessed. when transmitting in 9-bit data format and using 8-bit write instructions, write ?st to sci data register high (scidrh), then scidrl. module base + 0x_0006 76543210 rr8 t8 000000 w reset 0 0 0 00000 module base + 0x_0007 76543210 rr7r6r5r4r3r2r1r0 w t7 t6 t5 t4 t3 t2 t1 t0 reset 0 0 0 00100 = unimplemented or reserved figure 10-8. sci data registers (scidrh and scidrl) table 10-7. scidrh and scidrl field descriptions field description 7 r8 received bit 8 ?r8 is the ninth data bit received when the sci is con?ured for 9-bit data format (m = 1). 6 t8 transmit bit 8 ?t8 is the ninth data bit transmitted when the sci is con?ured for 9-bit data format (m = 1). 7? r[7:0] t[7:0] received bits ?received bits seven through zero for 9-bit or 8-bit data formats transmit bits ?transmit bits seven through zero for 9-bit or 8-bit formats chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 336 freescale semiconductor 10.4 functional description this section provides a complete functional description of the sci block, detailing the operation of the design from the end user perspective in a number of subsections. figure 10-9 shows the structure of the sci module. the sci allows full duplex, asynchronous, nrz serial communication between the cpu and remote devices, including other cpus. the sci transmitter and receiver operate independently, although they use the same baud rate generator. the cpu monitors the status of the sci, writes the data to be transmitted, and processes received data. figure 10-9. sci block diagram sci data receive shift register sci data register transmit shift register register baud rate generator sbr12?br0 bus transmit control 16 receive and wakeup data format control control t8 pf fe nf rdrf idle tie or tcie tdre tc r8 raf loops rwu re pe ilt pt wake m clock ilie rie rxd rsrc sbk loops te rsrc txd rdrf/or irq tdre irq idle irq tc irq irq to cpu chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 337 10.4.1 data format the sci uses the standard nrz mark/space data format illustrated in figure 10-10 below. figure 10-10. sci data formats each data character is contained in a frame that includes a start bit, eight or nine data bits, and a stop bit. clearing the m bit in sci control register 1 con?ures the sci for 8-bit data characters.a frame with eight data bits has a total of 10 bits. setting the m bit con?ures the sci for nine-bit data characters. a frame with nine data bits has a total of 11 bits when the sci is con?ured for 9-bit data characters, the ninth data bit is the t8 bit in sci data register high (scidrh). it remains unchanged after transmission and can be used repeatedly without rewriting it. a frame with nine data bits has a total of 11 bits. table 10-9. example of 9-bit data formats table 10-8. example of 8-bit data formats start bit data bits address bits parity bits stop bit 18 0 0 1 17 0 1 1 17 1 1 1 the address bit identi?s the frame as an address character. see section 10.4.4.6, ?eceiver wakeup . 01 start bit data bits address bits parity bits stop bit 19 0 0 1 18 0 1 1 18 1 1 1 the address bit identi?s the frame as an address character. see section 10.4.4.6, ?eceiver wakeup . 01 bit 5 start bit bit 0 bit 1 next stop bit start bit 9-bit data format bit 2 bit 3 bit 4 bit 6 bit 7 parity or data bit parity or data bit bit m in scicr1 set 8-bit data format bit m in scicr1 clear bit 5 bit 0 bit 1 bit 2 bit 3 bit 4 bit 6 bit 7 bit 8 stop bit next start bit start bit chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 338 freescale semiconductor 10.4.2 baud rate generation a 13-bit modulus counter in the baud rate generator derives the baud rate for both the receiver and the transmitter. the value from 0 to 8191 written to the sbr12?br0 bits determines the module clock divisor. the sbr bits are in the sci baud rate registers (scibdh and scibdl). the baud rate clock is synchronized with the bus clock and drives the receiver. the baud rate clock divided by 16 drives the transmitter. the receiver has an acquisition rate of 16 samples per bit time. baud rate generation is subject to one source of error: integer division of the module clock may not give the exact target frequency. table 10-10 lists some examples of achieving target baud rates with a module clock frequency of 25 mhz sci baud rate = sci module clock / (16 * scibr[12:0]) table 10-10. baud rates (example: module clock = 25 mhz) bits sbr[12-0] receiver clock (hz) transmitter clock (hz) target baud rate error (%) 41 609,756.1 38,109.8 38,400 .76 81 308,642.0 19,290.1 19,200 .47 163 153,374.2 9585.9 9600 .16 326 76,687.1 4792.9 4800 .15 651 38,402.5 2400.2 2400 .01 1302 19,201.2 1200.1 1200 .01 2604 9600.6 600.0 600 .00 5208 4800.0 300.0 300 .00 chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 339 10.4.3 transmitter figure 10-11. transmitter block diagram 10.4.3.1 transmitter character length the sci transmitter can accommodate either 8-bit or 9-bit data characters. the state of the m bit in sci control register 1 (scicr1) determines the length of data characters. when transmitting 9-bit data, bit t8 in sci data register high (scidrh) is the ninth bit (bit 8). 10.4.3.2 character transmission to transmit data, the mcu writes the data bits to the sci data registers (scidrh/scidrl), which in turn are transferred to the transmitter shift register. the transmit shift register then shifts a frame out through the tx output signal, after it has prefaced them with a start bit and appended them with a stop bit. the sci data registers (scidrh and scidrl) are the write-only buffers between the internal data bus and the transmit shift register. the sci also sets a ?g, the transmit data register empty ?g (tdre), every time it transfers data from the buffer (scidrh/l) to the transmitter shift register.the transmit driver routine may respond to this ?g by pe pt h876543210l 11-bit transmit shift register stop start t8 tdre tie tcie sbk tc parity generation msb sci data registers load from scidr shift enable preamble (all ones) break (all 0s) transmitter control m internal bus sbr12?br0 baud divider 16 tdre interrupt request tc interrupt request bus loop rsrc clock te to control rxd loops txd chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 340 freescale semiconductor writing another byte to the transmitter buffer (scidrh/scidrl), while the shift register is still shifting out the ?st byte. to initiate an sci transmission: 1. con?ure the sci: a) select a baud rate. write this value to the sci baud registers (scibdh/l) to begin the baud rate generator. remember that the baud rate generator is disabled when the baud rate is zero. writing to the scibdh has no effect without also writing to scibdl. b) write to scicr1 to con?ure word length, parity, and other con?uration bits (loops,rsrc,m,wake,ilt,pe,pt). c) enable the transmitter, interrupts, receive, and wake up as required, by writing to the scicr2 register bits (tie,tcie,rie,ilie,te,re,rwu,sbk). a preamble or idle character will now be shifted out of the transmitter shift register. 2. transmit procedure for each byte: a. poll the tdre flag by reading the scisr1 or responding to the tdre interrupt. keep in mind that the tdre bit resets to one. d) if the tdre ?g is set, write the data to be transmitted to scidrh/l, where the ninth bit is written to the t8 bit in scidrh if the sci is in 9-bit data format. a new transmission will not result until the tdre ?g has been cleared. 3. repeat step 2 for each subsequent transmission. note the tdre ?g is set when the shift register is loaded with the next data to be transmitted from scidrh/l, which happens, generally speaking, a little over half-way through the stop bit of the previous frame. speci?ally, this transfer occurs 9/16ths of a bit time after the start of the stop bit of the previous frame. writing the te bit from 0 to a 1 automatically loads the transmit shift register with a preamble of 10 logic 1s (if m = 0) or 11 logic 1s (if m = 1). after the preamble shifts out, control logic transfers the data from the sci data register into the transmit shift register. a logic 0 start bit automatically goes into the least signi?ant bit position of the transmit shift register. a logic 1 stop bit goes into the most signi?ant bit position. hardware supports odd or even parity. when parity is enabled, the most signi?ant bit (msb) of the data character is the parity bit. the transmit data register empty ?g, tdre, in sci status register 1 (scisr1) becomes set when the sci data register transfers a byte to the transmit shift register. the tdre ?g indicates that the sci data register can accept new data from the internal data bus. if the transmit interrupt enable bit, tie, in sci control register 2 (scicr2) is also set, the tdre ?g generates a transmitter interrupt request. when the transmit shift register is not transmitting a frame, the tx output signal goes to the idle condition, logic 1. if at any time software clears the te bit in sci control register 2 (scicr2), the transmitter enable signal goes low and the transmit signal goes idle. chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 341 if software clears te while a transmission is in progress (tc = 0), the frame in the transmit shift register continues to shift out. to avoid accidentally cutting off the last frame in a message, always wait for tdre to go high after the last frame before clearing te. to separate messages with preambles with minimum idle line time, use this sequence between messages: 1. write the last byte of the ?st message to scidrh/l. 2. wait for the tdre ?g to go high, indicating the transfer of the last frame to the transmit shift register. 3. queue a preamble by clearing and then setting the te bit. 4. write the ?st byte of the second message to scidrh/l. 10.4.3.3 break characters writing a logic 1 to the send break bit, sbk, in sci control register 2 (scicr2) loads the transmit shift register with a break character. a break character contains all logic 0s and has no start, stop, or parity bit. break character length depends on the m bit in sci control register 1 (scicr1). as long as sbk is at logic 1, transmitter logic continuously loads break characters into the transmit shift register. after software clears the sbk bit, the shift register ?ishes transmitting the last break character and then transmits at least one logic 1. the automatic logic 1 at the end of a break character guarantees the recognition of the start bit of the next frame. the sci recognizes a break character when a start bit is followed by eight or nine logic 0 data bits and a logic 0 where the stop bit should be. receiving a break character has these effects on sci registers: sets the framing error ?g, fe sets the receive data register full ?g, rdrf clears the sci data registers (scidrh/l) may set the overrun ?g, or, noise ?g, nf, parity error ?g, pe, or the receiver active ?g, raf (see section 10.3.2.4, ?ci status register 1 (scisr1) and section 10.3.2.5, ?ci status register 2 (scisr2) 10.4.3.4 idle characters an idle character contains all logic 1s and has no start, stop, or parity bit. idle character length depends on the m bit in sci control register 1 (scicr1). the preamble is a synchronizing idle character that begins the ?st transmission initiated after writing the te bit from 0 to 1. if the te bit is cleared during a transmission, the tx output signal becomes idle after completion of the transmission in progress. clearing and then setting the te bit during a transmission queues an idle character to be sent after the frame currently being transmitted. chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 342 freescale semiconductor note when queueing an idle character, return the te bit to logic 1 before the stop bit of the current frame shifts out through the tx output signal. setting te after the stop bit appears on tx output signal causes data previously written to the sci data register to be lost. toggle the te bit for a queued idle character while the tdre ?g is set and immediately before writing the next byte to the sci data register. note if the te bit is clear and the transmission is complete, the sci is not the master of the txd pin 10.4.4 receiver figure 10-12. sci receiver block diagram 10.4.4.1 receiver character length the sci receiver can accommodate either 8-bit or 9-bit data characters. the state of the m bit in sci control register 1 (scicr1) determines the length of data characters. when receiving 9-bit data, bit r8 in sci data register high (scidrh) is the ninth bit (bit 8). all ones m wake ilt pe pt re h876543210l 11-bit receive shift register stop start data wakeup parity checking msb sci data register r8 rie ilie rwu rdrf or nf fe pe internal bus bus idle interrupt request rdrf/or interrupt request sbr12?br0 baud divider loop rsrc from txd clock idle raf recovery control logic loops rxd chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 343 10.4.4.2 character reception during an sci reception, the receive shift register shifts a frame in from the rx input signal. the sci data register is the read-only buffer between the internal data bus and the receive shift register. after a complete frame shifts into the receive shift register, the data portion of the frame transfers to the sci data register. the receive data register full ?g, rdrf, in sci status register 1 (scisr1) becomes set, indicating that the received byte can be read. if the receive interrupt enable bit, rie, in sci control register 2 (scicr2) is also set, the rdrf ?g generates an rdrf interrupt request. 10.4.4.3 data sampling the receiver samples the rx input signal at the rt clock rate. the rt clock is an internal signal with a frequency 16 times the baud rate. to adjust for baud rate mismatch, the rt clock (see figure 10-13 ) is re-synchronized: after every start bit after the receiver detects a data bit change from logic 1 to logic 0 (after the majority of data bit samples at rt8, rt9, and rt10 returns a valid logic 1 and the majority of the next rt8, rt9, and rt10 samples returns a valid logic 0) to locate the start bit, data recovery logic does an asynchronous search for a logic 0 preceded by three logic 1s.when the falling edge of a possible start bit occurs, the rt clock begins to count to 16. figure 10-13. receiver data sampling to verify the start bit and to detect noise, data recovery logic takes samples at rt3, rt5, and rt7. table 10-11 summarizes the results of the start bit veri?ation samples. table 10-11. start bit veri?ation rt3, rt5, and rt7 samples start bit veri?ation noise flag 000 yes 0 001 yes 1 010 yes 1 011 no 0 reset rt clock rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt2 rt3 rt4 rt5 rt8 rt7 rt6 rt11 rt10 rt9 rt15 rt14 rt13 rt12 rt16 rt1 rt2 rt3 rt4 samples rt clock rt clock count start bit rx input signal start bit qualification start bit data sampling 11 1 1 1 1 110000 0 00 lsb verification chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 344 freescale semiconductor if start bit veri?ation is not successful, the rt clock is reset and a new search for a start bit begins. to determine the value of a data bit and to detect noise, recovery logic takes samples at rt8, rt9, and rt10. table 10-12 summarizes the results of the data bit samples. note the rt8, rt9, and rt10 samples do not affect start bit veri?ation. if any or all of the rt8, rt9, and rt10 start bit samples are logic 1s following a successful start bit veri?ation, the noise ?g (nf) is set and the receiver assumes that the bit is a start bit (logic 0). to verify a stop bit and to detect noise, recovery logic takes samples at rt8, rt9, and rt10. table 10-13 summarizes the results of the stop bit samples. table 10-13. stop bit recovery 100 yes 1 101 no 0 110 no 0 111 no 0 table 10-12. data bit recovery rt8, rt9, and rt10 samples data bit determination noise flag 000 0 0 001 0 1 010 0 1 011 1 1 100 0 1 101 1 1 110 1 1 111 1 0 rt8, rt9, and rt10 samples framing error flag noise flag 000 1 0 001 1 1 010 1 1 011 0 1 100 1 1 101 0 1 110 0 1 111 0 0 table 10-11. start bit veri?ation rt3, rt5, and rt7 samples start bit veri?ation noise flag chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 345 in figure 10-14 the veri?ation samples rt3 and rt5 determine that the ?st low detected was noise and not the beginning of a start bit. the rt clock is reset and the start bit search begins again. the noise ?g is not set because the noise occurred before the start bit was found. figure 10-14. start bit search example 1 in figure 10-15 , veri?ation sample at rt3 is high. the rt3 sample sets the noise ?g. although the perceived bit time is misaligned, the data samples rt8, rt9, and rt10 are within the bit time and data recovery is successful. figure 10-15. start bit search example 2 reset rt clock rt1 rt1 rt1 rt1 rt2 rt3 rt4 rt5 rt1 rt1 rt2 rt3 rt4 rt7 rt6 rt5 rt10 rt9 rt8 rt14 rt13 rt12 rt11 rt15 rt16 rt1 rt2 rt3 samples rt clock rt clock count start bit rx input signal 11 0 1 111000 00 lsb 0 0 reset rt clock rt1 rt1 rt1 rt1 rt1 rt1 rt2 rt3 rt4 rt5 rt6 rt7 rt8 rt11 rt10 rt9 rt14 rt13 rt12 rt2 rt1 rt16 rt15 rt3 rt4 rt5 rt6 rt7 samples rt clock rt clock count actual start bit rx input signal 11 1 1 11000 0 lsb 0 0 perceived start bit chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 346 freescale semiconductor in figure 10-16 , a large burst of noise is perceived as the beginning of a start bit, although the test sample at rt5 is high. the rt5 sample sets the noise ?g. although this is a worst-case misalignment of perceived bit time, the data samples rt8, rt9, and rt10 are within the bit time and data recovery is successful. figure 10-16. start bit search example 3 figure 10-17 shows the effect of noise early in the start bit time. although this noise does not affect proper synchronization with the start bit time, it does set the noise ?g. figure 10-17. start bit search example 4 reset rt clock rt1 rt1 rt1 rt1 rt2 rt3 rt4 rt5 rt6 rt7 rt8 rt9 rt10 rt13 rt12 rt11 rt16 rt15 rt14 rt4 rt3 rt2 rt1 rt5 rt6 rt7 rt8 rt9 samples rt clock rt clock count actual start bit rx input signal 10 1 11000 0 lsb 0 perceived start bit reset rt clock rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt2 rt3 rt4 rt7 rt6 rt5 rt10 rt9 rt8 rt14 rt13 rt12 rt11 rt15 rt16 rt1 rt2 rt3 samples rt clock rt clock count perceived and actual start bit rx input signal 11 1 1100 1 lsb 1 1 1 1 chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 347 figure 10-18 shows a burst of noise near the beginning of the start bit that resets the rt clock. the sample after the reset is low but is not preceded by three high samples that would qualify as a falling edge. depending on the timing of the start bit search and on the data, the frame may be missed entirely or it may set the framing error ?g. figure 10-18. start bit search example 5 in figure 10-19 , a noise burst makes the majority of data samples rt8, rt9, and rt10 high. this sets the noise ?g but does not reset the rt clock. in start bits only, the rt8, rt9, and rt10 data samples are ignored. figure 10-19. start bit search example 6 reset rt clock rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt2 rt3 rt4 rt7 rt6 rt5 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 samples rt clock rt clock count start bit rx input signal 11 1 1101 0 lsb 1 1 1 1 1 00 0 00 0 0 0 no start bit found reset rt clock rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt1 rt2 rt3 rt4 rt7 rt6 rt5 rt10 rt9 rt8 rt14 rt13 rt12 rt11 rt15 rt16 rt1 rt2 rt3 samples rt clock rt clock count start bit rx input signal 11 1 1100 0 lsb 1 1 1 1 0 11 0 chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 348 freescale semiconductor 10.4.4.4 framing errors if the data recovery logic does not detect a logic 1 where the stop bit should be in an incoming frame, it sets the framing error ?g, fe, in sci status register 1 (scisr1). a break character also sets the fe ?g because a break character has no stop bit. the fe ?g is set at the same time that the rdrf ?g is set. 10.4.4.5 baud rate tolerance a transmitting device may be operating at a baud rate below or above the receiver baud rate. accumulated bit time misalignment can cause one of the three stop bit data samples (rt8, rt9, and rt10) to fall outside the actual stop bit.a noise error will occur if the rt8, rt9, and rt10 samples are not all the same logical values. a framing error will occur if the receiver clock is misaligned in such a way that the majority of the rt8, rt9, and rt10 stop bit samples are a logic zero. as the receiver samples an incoming frame, it re-synchronizes the rt clock on any valid falling edge within the frame. re synchronization within frames will correct a misalignment between transmitter bit times and receiver bit times. 10.4.4.5.1 slow data tolerance figure 10-20 shows how much a slow received frame can be misaligned without causing a noise error or a framing error. the slow stop bit begins at rt8 instead of rt1 but arrives in time for the stop bit data samples at rt8, rt9, and rt10. figure 10-20. slow data let s take rtr as receiver rt clock and rtt as transmitter rt clock. for an 8-bit data character, it takes the receiver 9 bit times x 16 rtr cycles +7 rtr cycles =151 rtr cycles to start data sampling of the stop bit. with the misaligned character shown in figure 10-20 , the receiver counts 151 rtr cycles at the point when the count of the transmitting device is 9 bit times x 16 rtt cycles = 144 rtt cycles. the maximum percent difference between the receiver count and the transmitter count of a slow 8-bit data character with no errors is: ((151 ?144) / 151) x 100 = 4.63% for a 9-bit data character, it takes the receiver 10 bit times x 16 rtr cycles + 7 rtr cycles = 167 rtr cycles to start data sampling of the stop bit. msb stop rt1 rt2 rt3 rt4 rt5 rt6 rt7 rt8 rt9 rt10 rt11 rt12 rt13 rt14 rt15 rt16 data samples receiver rt clock chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 349 with the misaligned character shown in figure 10-20 , the receiver counts 167 rtr cycles at the point when the count of the transmitting device is 10 bit times x 16 rtt cycles = 160 rtt cycles. the maximum percent difference between the receiver count and the transmitter count of a slow 9-bit character with no errors is: ((167 ?160) / 167) x 100 = 4.19% 10.4.4.5.2 fast data tolerance figure 10-21 shows how much a fast received frame can be misaligned. the fast stop bit ends at rt10 instead of rt16 but is still sampled at rt8, rt9, and rt10. figure 10-21. fast data for an 8-bit data character, it takes the receiver 9 bit times x 16 rtr cycles + 10 rtr cycles = 154 rtr cycles to ?ish data sampling of the stop bit. with the misaligned character shown in figure 10-21 , the receiver counts 154 rtr cycles at the point when the count of the transmitting device is 10 bit times x 16 rtt cycles = 160 rtt cycles. the maximum percent difference between the receiver count and the transmitter count of a fast 8-bit character with no errors is: ((160 ?154) / 160) x 100 = 3.75% for a 9-bit data character, it takes the receiver 10 bit times x 16 rtr cycles + 10 rtr cycles = 170 rtr cycles to ?ish data sampling of the stop bit. with the misaligned character shown in figure 10-21 , the receiver counts 170 rtr cycles at the point when the count of the transmitting device is 11 bit times x 16 rtt cycles = 176 rtt cycles. the maximum percent difference between the receiver count and the transmitter count of a fast 9-bit character with no errors is: ((176 ?170) / 176) x 100 = 3.40% 10.4.4.6 receiver wakeup to enable the sci to ignore transmissions intended only for other receivers in multiple-receiver systems, the receiver can be put into a standby state. setting the receiver wakeup bit, rwu, in sci control register 2 (scicr2) puts the receiver into standby state during which receiver interrupts are disabled.the sci will still load the receive data into the scidrh/l registers, but it will not set the rdrf ?g. idle or next frame stop rt1 rt2 rt3 rt4 rt5 rt6 rt7 rt8 rt9 rt10 rt11 rt12 rt13 rt14 rt15 rt16 data samples receiver rt clock chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 350 freescale semiconductor the transmitting device can address messages to selected receivers by including addressing information in the initial frame or frames of each message. the wake bit in sci control register 1 (scicr1) determines how the sci is brought out of the standby state to process an incoming message. the wake bit enables either idle line wakeup or address mark wakeup. 10.4.4.6.1 idle input line wakeup (wake = 0) in this wakeup method, an idle condition on the rx input signal clears the rwu bit and wakes up the sci. the initial frame or frames of every message contain addressing information. all receivers evaluate the addressing information, and receivers for which the message is addressed process the frames that follow. any receiver for which a message is not addressed can set its rwu bit and return to the standby state. the rwu bit remains set and the receiver remains on standby until another idle character appears on the rx input signal. idle line wakeup requires that messages be separated by at least one idle character and that no message contains idle characters. the idle character that wakes a receiver does not set the receiver idle bit, idle, or the receive data register full ?g, rdrf. the idle line type bit, ilt, determines whether the receiver begins counting logic 1s as idle character bits after the start bit or after the stop bit. ilt is in sci control register 1 (scicr1). 10.4.4.6.2 address mark wakeup (wake = 1) in this wakeup method, a logic 1 in the most signi?ant bit (msb) position of a frame clears the rwu bit and wakes up the sci. the logic 1 in the msb position marks a frame as an address frame that contains addressing information. all receivers evaluate the addressing information, and the receivers for which the message is addressed process the frames that follow.any receiver for which a message is not addressed can set its rwu bit and return to the standby state. the rwu bit remains set and the receiver remains on standby until another address frame appears on the rx input signal. the logic 1 msb of an address frame clears the receiver s rwu bit before the stop bit is received and sets the rdrf ?g. address mark wakeup allows messages to contain idle characters but requires that the msb be reserved for use in address frames.{sci_wake} note with the wake bit clear, setting the rwu bit after the rx input signal has been idle can cause the receiver to wake up immediately. chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 351 10.4.5 single-wire operation normally, the sci uses two pins for transmitting and receiving. in single-wire operation, the rxd pin is disconnected from the sci. the sci uses the txd pin for both receiving and transmitting. figure 10-22. single-wire operation (loops = 1, rsrc = 1) enable single-wire operation by setting the loops bit and the receiver source bit, rsrc, in sci control register 1 (scicr1). setting the loops bit disables the path from the rx input signal to the receiver. setting the rsrc bit connects the receiver input to the output of the txd pin driver. both the transmitter and receiver must be enabled (te = 1 and re = 1).the txdir bit (scisr2[1]) determines whether the txd pin is going to be used as an input (txdir = 0) or an output (txdir = 1) in this mode of operation. 10.4.6 loop operation in loop operation the transmitter output goes to the receiver input. the rx input signal is disconnected from the sci . figure 10-23. loop operation (loops = 1, rsrc = 0) enable loop operation by setting the loops bit and clearing the rsrc bit in sci control register 1 (scicr1). setting the loops bit disables the path from the rx input signal to the receiver. clearing the rsrc bit connects the transmitter output to the receiver input. both the transmitter and receiver must be enabled (te = 1 and re = 1). 10.5 initialization information 10.5.1 reset initialization the reset state of each individual bit is listed in section 10.3, ?emory map and registers which details the registers and their bit ?lds. all special functions or modes which are initialized during or just following reset are described within this section. rxd transmitter receiver tx output signal tx input signal rxd transmitter receiver tx output signal chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 352 freescale semiconductor 10.5.2 interrupt operation 10.5.2.1 system level interrupt sources there are ve interrupt sources that can generate an sci interrupt in to the cpu. they are listed in table 10-14 . table 10-14. sci interrupt source interrupt source flag local enable transmitter tdre tie transmitter tc tcie receiver rdrf rie or receiver idle ilie chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 353 10.5.2.2 interrupt descriptions the sci only originates interrupt requests. the following is a description of how the sci makes a request and how the mcu should acknowledge that request. the interrupt vector offset and interrupt number are chip dependent. the sci only has a single interrupt line ( sci interrupt signal , active high operation) and all the following interrupts, when generated, are ored together and issued through that port. 10.5.2.2.1 tdre description the tdre interrupt is set high by the sci when the transmit shift register receives a byte from the sci data register. a tdre interrupt indicates that the transmit data register (scidrh/l) is empty and that a new byte can be written to the scidrh/l for transmission.clear tdre by reading sci status register 1 with tdre set and then writing to sci data register low (scidrl). 10.5.2.2.2 tc description the tc interrupt is set by the sci when a transmission has been completed.a tc interrupt indicates that there is no transmission in progress. tc is set high when the tdre ?g is set and no data, preamble, or break character is being transmitted. when tc is set, the txd pin becomes idle (logic 1). clear tc by reading sci status register 1 (scisr1) with tc set and then writing to sci data register low (scidrl).tc is cleared automatically when data, preamble, or break is queued and ready to be sent. 10.5.2.2.3 rdrf description the rdrf interrupt is set when the data in the receive shift register transfers to the sci data register. a rdrf interrupt indicates that the received data has been transferred to the sci data register and that the byte can now be read by the mcu. the rdrf interrupt is cleared by reading the sci status register one (scisr1) and then reading sci data register low (scidrl). 10.5.2.2.4 or description the or interrupt is set when software fails to read the sci data register before the receive shift register receives the next frame. the newly acquired data in the shift register will be lost in this case, but the data already in the sci data registers is not affected. the or interrupt is cleared by reading the sci status register one (scisr1) and then reading sci data register low (scidrl). 10.5.2.3 idle description the idle interrupt is set when 10 consecutive logic 1s (if m = 0) or 11 consecutive logic 1s (if m = 1) appear on the receiver input. once the idle is cleared, a valid frame must again set the rdrf ?g before an idle condition can set the idle ?g. clear idle by reading sci status register 1 (scisr1) with idle set and then reading sci data register low (scidrl). 10.5.3 recovery from wait mode the sci interrupt request can be used to bring the cpu out of wait mode. chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 354 freescale semiconductor chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 355 chapter 10 serial communications interface (sciv1) mc9s12kg128 data sheet, rev. 1.15 356 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 357 chapter 11 serial peripheral interface (spiv3) 11.1 introduction the spi module allows a duplex, synchronous, serial communication between the mcu and peripheral devices. software can poll the spi status ?gs or the spi operation can be interrupt driven. 11.1.1 features the spi includes these distinctive features: master mode and slave mode bidirectional mode slave select output mode fault error ?g with cpu interrupt capability double-buffered data register serial clock with programmable polarity and phase control of spi operation during wait mode 11.1.2 modes of operation the spi functions in three modes, run, wait, and stop. run mode this is the basic mode of operation. wait mode spi operation in wait mode is a con?urable low power mode, controlled by the spiswai bit located in the spicr2 register. in wait mode, if the spiswai bit is clear, the spi operates like in run mode. if the spiswai bit is set, the spi goes into a power conservative state, with the spi clock generation turned off. if the spi is con?ured as a master, any transmission in progress stops, but is resumed after cpu goes into run mode. if the spi is con?ured as a slave, reception and transmission of a byte continues, so that the slave stays synchronized to the master. stop mode the spi is inactive in stop mode for reduced power consumption. if the spi is con?ured as a master, any transmission in progress stops, but is resumed after cpu goes into run mode. if the spi is con?ured as a slave, reception and transmission of a byte continues, so that the slave stays synchronized to the master. this is a high level description only, detailed descriptions of operating modes are contained in section 11.4, ?unctional description . chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 358 freescale semiconductor 11.1.3 block diagram figure 11-1 gives an overview on the spi architecture. the main parts of the spi are status, control, and data registers, shifter logic, baud rate generator, master/slave control logic, and port control logic. figure 11-1. spi block diagram 11.2 external signal description this section lists the name and description of all ports including inputs and outputs that do, or may, connect off chip. the spi module has a total of four external pins. 11.2.1 mosi ?master out/slave in pin this pin is used to transmit data out of the spi module when it is con?ured as a master and receive data when it is con?ured as slave. spi control register 1 spi control register 2 spi baud rate register spi status register spi data register shifter port control logic mosi sck interrupt control spi msb lsb lsbfe=1 lsbfe=0 lsbfe=0 lsbfe=1 data in lsbfe=1 lsbfe=0 data out 8 8 baud rate generator prescaler bus clock counter clock select sppr 3 3 spr baud rate phase + polarity control master slave sck in sck out master baud rate slave baud rate phase + polarity control control control cpol cpha 2 bidiroe spc0 2 modf spif sptef spi request interrupt ss shift clock sample clock chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 359 11.2.2 miso ?master in/slave out pin this pin is used to transmit data out of the spi module when it is con?ured as a slave and receive data when it is con?ured as master. 11.2.3 ss ?slave select pin this pin is used to output the select signal from the spi module to another peripheral with which a data transfer is to take place when its con?ured as a master and its used as an input to receive the slave select signal when the spi is con?ured as slave. 11.2.4 sck ?serial clock pin this pin is used to output the clock with respect to which the spi transfers data or receive clock in case of slave. 11.3 memory map and register de?ition this section provides a detailed description of address space and registers used by the spi. the memory map for the spi is given below in table 11-1 . the address listed for each register is the sum of a base address and an address offset. the base address is de?ed at the soc level and the address offset is de?ed at the module level. reads from the reserved bits return zeros and writes to the reserved bits have no effect. 11.3.1 module memory map table 11-1. spi memory map address use access 0x0000 spi control register 1 (spicr1) r/w 0x0001 spi control register 2 (spicr2) r/w 1 1 certain bits are non-writable. 0x0002 spi baud rate register (spibr) r/w 1 0x0003 spi status register (spisr) r 2 2 writes to this register are ignored. 0x0004 reserved 2,3 3 reading from this register returns all zeros. 0x0005 spi data register (spidr) r/w 0x0006 reserved 2,3 0x0007 reserved 2,3 chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 360 freescale semiconductor 11.3.2 register descriptions this section consists of register descriptions in address order. each description includes a standard register diagram with an associated ?ure number. details of register bit and ?ld function follow the register diagrams, in bit order. 11.3.2.1 spi control register 1 (spicr1) read: anytime write: anytime name 7 6 5 4 3 2 1 0 spicr1 r spie spe sptie mstr cpol cpha ssoe lsbfe w spicr2 r0 0 0 modfen bidiroe 0 spiswai spc0 w spibr r0 sppr2 sppr1 sppr0 0 spr2 spr1 spr0 w spisr r spif 0 sptef modf 0 0 0 0 w reserved r w spidr r bit 7 6 5 4 3 2 2 bit 0 w reserved r w reserved r w = unimplemented or reserved figure 11-2. spi register summary 76543210 r spie spe sptie mstr cpol cpha ssoe lsbfe w reset 0 0 0 00100 figure 11-3. spi control register 1 (spicr1) chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 361 table 11-2. spicr1 field descriptions field description 7 spie spi interrupt enable bit ?this bit enables spi interrupt requests, if spif or modf status ?g is set. 0 spi interrupts disabled. 1 spi interrupts enabled. 6 spe spi system enable bit ?this bit enables the spi system and dedicates the spi port pins to spi system functions. if spe is cleared, spi is disabled and forced into idle state, status bits in spisr register are reset. 0 spi disabled (lower power consumption). 1 spi enabled, port pins are dedicated to spi functions. 5 sptie spi transmit interrupt enable ?this bit enables spi interrupt requests, if sptef ?g is set. 0 sptef interrupt disabled. 1 sptef interrupt enabled. 4 mstr spi master/slave mode select bit ?this bit selects, if the spi operates in master or slave mode. switching the spi from master to slave or vice versa forces the spi system into idle state. 0 spi is in slave mode 1 spi is in master mode 3 cpol spi clock polarity bit this bit selects an inverted or non-inverted spi clock. to transmit data between spi modules, the spi modules must have identical cpol values. in master mode, a change of this bit will abort a transmission in progress and force the spi system into idle state. 0 active-high clocks selected. in idle state sck is low. 1 active-low clocks selected. in idle state sck is high. 2 cpha spi clock phase bit this bit is used to select the spi clock format. in master mode, a change of this bit will abort a transmission in progress and force the spi system into idle state. 0 sampling of data occurs at odd edges (1,3,5,...,15) of the sck clock 1 sampling of data occurs at even edges (2,4,6,...,16) of the sck clock 1 ssoe slave select output enable ?the ss output feature is enabled only in master mode, if modfen is set, by asserting the ssoe as shown in table 11-3 . in master mode, a change of this bit will abort a transmission in progress and force the spi system into idle state. 0 lsbfe lsb-first enable ?this bit does not affect the position of the msb and lsb in the data register. reads and writes of the data register always have the msb in bit 7. in master mode, a change of this bit will abort a transmission in progress and force the spi system into idle state. 0 data is transferred most signi?ant bit ?st. 1 data is transferred least signi?ant bit ?st. table 11-3. ss input / output selection modfen ssoe master mode slave mode 00 ss not used by spi ss input 01 ss not used by spi ss input 10 ss input with modf feature ss input 11 ss is slave select output ss input chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 362 freescale semiconductor 11.3.2.2 spi control register 2 (spicr2) read: anytime write: anytime; writes to the reserved bits have no effect 76543210 r000 modfen bidiroe 0 spiswai spc0 w reset 0 0 0 00000 = unimplemented or reserved figure 11-4. spi control register 2 (spicr2) table 11-4. spicr2 field descriptions field description 4 modfen mode fault enable bit ?this bit allows the modf failure being detected. if the spi is in master mode and modfen is cleared, then the ss port pin is not used by the spi. in slave mode, the ss is available only as an input regardless of the value of modfen. for an overview on the impact of the modfen bit on the ss port pin con?uration refer to table 11-3 . in master mode, a change of this bit will abort a transmission in progress and force the spi system into idle state. 0 ss port pin is not used by the spi 1 ss port pin with modf feature 3 bidiroe output enable in the bidirectional mode of operation this bit controls the mosi and miso output buffer of the spi, when in bidirectional mode of operation (spc0 is set). in master mode this bit controls the output buffer of the mosi port, in slave mode it controls the output buffer of the miso port. in master mode, with spc0 set, a change of this bit will abort a transmission in progress and force the spi into idle state. 0 output buffer disabled 1 output buffer enabled 1 spiswai spi stop in wait mode bit ?this bit is used for power conservation while in wait mode. 0 spi clock operates normally in wait mode 1 stop spi clock generation when in wait mode 0 spc0 serial pin control bit 0 ?this bit enables bidirectional pin con?urations as shown in table 11-5 . in master mode, a change of this bit will abort a transmission in progress and force the spi system into idle state table 11-5. bidirectional pin con?urations pin mode spc0 bidiroe miso mosi master mode of operation normal 0 x master in master out bidirectional 1 0 miso not used by spi master in 1 master i/o slave mode of operation normal 0 x slave out slave in bidirectional 1 0 slave in mosi not used by spi 1 slave i/o chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 363 11.3.2.3 spi baud rate register (spibr) read: anytime write: anytime; writes to the reserved bits have no effect the baud rate divisor equation is as follows: the baud rate can be calculated with the following equation: 76543210 r0 sppr2 sppr1 sppr0 0 spr2 spr1 spr0 w reset 0 0 0 00000 = unimplemented or reserved figure 11-5. spi baud rate register (spibr) table 11-6. spibr field descriptions field description 6:4 sppr[2:0] spi baud rate preselection bits ?these bits specify the spi baud rates as shown in table 11-7 . in master mode, a change of these bits will abort a transmission in progress and force the spi system into idle state. 2:0 spr[2:0} spi baud rate selection bits these bits specify the spi baud rates as shown in table 11-7 . in master mode, a change of these bits will abort a transmission in progress and force the spi system into idle state. baudratedivisor sppr 1 + () 2 ? spr 1 + () = baud rate busclock baudratedivisor ? = chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 364 freescale semiconductor table 11-7. example spi baud rate selection (25 mhz bus clock) sppr2 sppr1 sppr0 spr2 spr1 spr0 baud rate divisor baud rate 0000002 12.5 mhz 0000014 6.25 mhz 0000108 3.125 mhz 00001116 1.5625 mhz 00010032 781.25 khz 00010164 390.63 khz 000110128 195.31 khz 000111256 97.66 khz 0010004 6.25 mhz 0010018 3.125 mhz 00101016 1.5625 mhz 00101132 781.25 khz 00110064 390.63 khz 001101128 195.31 khz 001110256 97.66 khz 001111512 48.83 khz 0100006 4.16667 mhz 01000112 2.08333 mhz 01001024 1.04167 mhz 01001148 520.83 khz 01010096 260.42 khz 010101192 130.21 khz 010110384 65.10 khz 010111768 32.55 khz 0110008 3.125 mhz 01100116 1.5625 mhz 01101032 781.25 khz 01101164 390.63 khz 011100128 195.31 khz 011101256 97.66 khz 011110512 48.83 khz 011111 1024 24.41 khz 10000010 2.5 mhz 10000120 1.25 mhz 10001040 625 khz 10001180 312.5 khz 100100160 156.25 khz 100101320 78.13 khz 100110640 39.06 khz chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 365 note in slave mode of spi s-clock speed div2 is not supported. 100111 1280 19.53 khz 10100012 2.08333 mhz 10100124 1.04167 mhz 10101048 520.83 khz 10101196 260.42 khz 101100192 130.21 khz 101101384 65.10 khz 101110768 32.55 khz 101111 1536 16.28 khz 11000014 1.78571 mhz 11000128 892.86 khz 11001056 446.43 khz 110011112 223.21 khz 110100224 111.61 khz 110101448 55.80 khz 110110896 27.90 khz 110111 1792 13.95 khz 11100016 1.5625 mhz 11100132 781.25 khz 11101064 390.63 khz 111011128 195.31 khz 111100256 97.66 khz 111101512 48.83 khz 111110 1024 24.41 khz 111111 2048 12.21 khz table 11-7. example spi baud rate selection (25 mhz bus clock) (continued) sppr2 sppr1 sppr0 spr2 spr1 spr0 baud rate divisor baud rate chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 366 freescale semiconductor 11.3.2.4 spi status register (spisr) read: anytime write: has no effect 11.3.2.5 spi data register (spidr) read: anytime; normally read only after spif is set write: anytime 76543210 r spif 0 sptef modf 0000 w reset 0 0 1 00000 = unimplemented or reserved figure 11-6. spi status register (spisr) table 11-8. spisr field descriptions field description 7 spif spif interrupt flag this bit is set after a received data byte has been transferred into the spi data register. this bit is cleared by reading the spisr register (with spif set) followed by a read access to the spi data register. 0 transfer not yet complete 1 new data copied to spidr 5 sptef spi transmit empty interrupt flag if set, this bit indicates that the transmit data register is empty. to clear this bit and place data into the transmit data register, spisr has to be read with sptef = 1, followed by a write to spidr. any write to the spi data register without reading sptef = 1, is effectively ignored. 0 spi data register not empty 1 spi data register empty 4 modf mode fault flag this bit is set if the ss input becomes low while the spi is con?ured as a master and mode fault detection is enabled, modfen bit of spicr2 register is set. refer to modfen bit description in section 11.3.2.2, ?pi control register 2 (spicr2) . the ?g is cleared automatically by a read of the spi status register (with modf set) followed by a write to the spi control register 1. 0 mode fault has not occurred. 1 mode fault has occurred. 76543210 r bit 7 6 5 4322 bit 0 w reset 0 0 0 00000 = unimplemented or reserved figure 11-7. spi data register (spidr) chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 367 the spi data register is both the input and output register for spi data. a write to this register allows a data byte to be queued and transmitted. for a spi con?ured as a master, a queued data byte is transmitted immediately after the previous transmission has completed. the spi transmitter empty flag sptef in the spisr register indicates when the spi data register is ready to accept new data. reading the data can occur anytime from after the spif is set to before the end of the next transfer. if the spif is not serviced by the end of the successive transfers, those data bytes are lost and the data within the spidr retains the ?st byte until spif is serviced. 11.4 functional description the spi module allows a duplex, synchronous, serial communication between the mcu and peripheral devices. software can poll the spi status ?gs or spi operation can be interrupt driven. the spi system is enabled by setting the spi enable (spe) bit in spi control register 1. while spe bit is set, the four associated spi port pins are dedicated to the spi function as: slave select ( ss) serial clock (sck) master out/slave in (mosi) master in/slave out (miso) the main element of the spi system is the spi data register. the 8-bit data register in the master and the 8-bit data register in the slave are linked by the mosi and miso pins to form a distributed 16-bit register. when a data transfer operation is performed, this 16-bit register is serially shifted eight bit positions by the s-clock from the master, so data is exchanged between the master and the slave. data written to the master spi data register becomes the output data for the slave, and data read from the master spi data register after a transfer operation is the input data from the slave. a read of spisr with sptef = 1 followed by a write to spidr puts data into the transmit data register. when a transfer is complete, received data is moved into the receive data register. data may be read from this double-buffered system any time before the next transfer has completed. this 8-bit data register acts as the spi receive data register for reads and as the spi transmit data register for writes. a single spi register address is used for reading data from the read data buffer and for writing data to the transmit data register. the clock phase control bit (cpha) and a clock polarity control bit (cpol) in the spi control register 1 (spicr1) select one of four possible clock formats to be used by the spi system. the cpol bit simply selects a non-inverted or inverted clock. the cpha bit is used to accommodate two fundamentally different protocols by sampling data on odd numbered sck edges or on even numbered sck edges (see section 11.4.3, ?ransmission formats ). the spi can be con?ured to operate as a master or as a slave. when the mstr bit in spi control register1 is set, master mode is selected, when the mstr bit is clear, slave mode is selected. chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 368 freescale semiconductor 11.4.1 master mode the spi operates in master mode when the mstr bit is set. only a master spi module can initiate transmissions. a transmission begins by writing to the master spi data register. if the shift register is empty, the byte immediately transfers to the shift register. the byte begins shifting out on the mosi pin under the control of the serial clock. s-clock the spr2, spr1, and spr0 baud rate selection bits in conjunction with the sppr2, sppr1, and sppr0 baud rate preselection bits in the spi baud rate register control the baud rate generator and determine the speed of the transmission. the sck pin is the spi clock output. through the sck pin, the baud rate generator of the master controls the shift register of the slave peripheral. mosi and miso pins in master mode, the function of the serial data output pin (mosi) and the serial data input pin (miso) is determined by the spc0 and bidiroe control bits. ss pin if modfen and ssoe bit are set, the ss pin is con?ured as slave select output. the ss output becomes low during each transmission and is high when the spi is in idle state. if modfen is set and ssoe is cleared, the ss pin is con?ured as input for detecting mode fault error. if the ss input becomes low this indicates a mode fault error where another master tries to drive the mosi and sck lines. in this case, the spi immediately switches to slave mode, by clearing the mstr bit and also disables the slave output buffer miso (or siso in bidirectional mode). so the result is that all outputs are disabled and sck, mosi and miso are inputs. if a transmission is in progress when the mode fault occurs, the transmission is aborted and the spi is forced into idle state. this mode fault error also sets the mode fault (modf) ?g in the spi status register (spisr). if the spi interrupt enable bit (spie) is set when the modf ?g gets set, then an spi interrupt sequence is also requested. when a write to the spi data register in the master occurs, there is a half sck-cycle delay. after the delay, sck is started within the master. the rest of the transfer operation differs slightly, depending on the clock format speci?d by the spi clock phase bit, cpha, in spi control register 1 (see section 11.4.3, ?ransmission formats ). note a change of the bits cpol, cpha, ssoe, lsbfe, modfen, spc0, bidiroe with spc0 set, sppr2?ppr0 and spr2?pr0 in master mode will abort a transmission in progress and force the spi into idle state. the remote slave cannot detect this, therefore the master has to ensure that the remote slave is set back to idle state. chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 369 11.4.2 slave mode the spi operates in slave mode when the mstr bit in spi control register1 is clear. sck clock in slave mode, sck is the spi clock input from the master. miso and mosi pins in slave mode, the function of the serial data output pin (miso) and serial data input pin (mosi) is determined by the spc0 bit and bidiroe bit in spi control register 2. ss pin the ss pin is the slave select input. before a data transmission occurs, the ss pin of the slave spi must be low. ss must remain low until the transmission is complete. if ss goes high, the spi is forced into idle state. the ss input also controls the serial data output pin, if ss is high (not selected), the serial data output pin is high impedance, and, if ss is low the ?st bit in the spi data register is driven out of the serial data output pin. also, if the slave is not selected ( ss is high), then the sck input is ignored and no internal shifting of the spi shift register takes place. although the spi is capable of duplex operation, some spi peripherals are capable of only receiving spi data in a slave mode. for these simpler devices, there is no serial data out pin. note when peripherals with duplex capability are used, take care not to simultaneously enable two receivers whose serial outputs drive the same system slave s serial data output line. as long as no more than one slave device drives the system slave s serial data output line, it is possible for several slaves to receive the same transmission from a master, although the master would not receive return information from all of the receiving slaves. if the cpha bit in spi control register 1 is clear, odd numbered edges on the sck input cause the data at the serial data input pin to be latched. even numbered edges cause the value previously latched from the serial data input pin to shift into the lsb or msb of the spi shift register, depending on the lsbfe bit. if the cpha bit is set, even numbered edges on the sck input cause the data at the serial data input pin to be latched. odd numbered edges cause the value previously latched from the serial data input pin to shift into the lsb or msb of the spi shift register, depending on the lsbfe bit. when cpha is set, the ?st edge is used to get the ?st data bit onto the serial data output pin. when cpha is clear and the ss input is low (slave selected), the ?st bit of the spi data is driven out of the serial data output pin. after the eighth shift, the transfer is considered complete and the received data is transferred into the spi data register. to indicate transfer is complete, the spif ?g in the spi status register is set. note a change of the bits cpol, cpha, ssoe, lsbfe, modfen, spc0 and bidiroe with spc0 set in slave mode will corrupt a transmission in progress and has to be avoided. chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 370 freescale semiconductor 11.4.3 transmission formats during an spi transmission, data is transmitted (shifted out serially) and received (shifted in serially) simultaneously. the serial clock (sck) synchronizes shifting and sampling of the information on the two serial data lines. a slave select line allows selection of an individual slave spi device, slave devices that are not selected do not interfere with spi bus activities. optionally, on a master spi device, the slave select line can be used to indicate multiple-master bus contention. figure 11-8. master/slave transfer block diagram 11.4.3.1 clock phase and polarity controls using two bits in the spi control register1, software selects one of four combinations of serial clock phase and polarity. the cpol clock polarity control bit speci?s an active high or low clock and has no signi?ant effect on the transmission format. the cpha clock phase control bit selects one of two fundamentally different transmission formats. clock phase and polarity should be identical for the master spi device and the communicating slave device. in some cases, the phase and polarity are changed between transmissions to allow a master device to communicate with peripheral slaves having different requirements. 11.4.3.2 cpha = 0 transfer format the ?st edge on the sck line is used to clock the ?st data bit of the slave into the master and the ?st data bit of the master into the slave. in some peripherals, the ?st bit of the slave s data is available at the slave s data out pin as soon as the slave is selected. in this format, the ?st sck edge is issued a half cycle after ss has become low. a half sck cycle later, the second edge appears on the sck line. when this second edge occurs, the value previously latched from the serial data input pin is shifted into the lsb or msb of the shift register, depending on lsbfe bit. after this second edge, the next bit of the spi master data is transmitted out of the serial data output pin of the master to the serial input pin on the slave. this process continues for a total of 16 edges on the sck line, with data being latched on odd numbered edges and shifted on even numbered edges. shift register shift register baud rate generator master spi slave spi mosi mosi miso miso sck sck ss ss v dd chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 371 data reception is double buffered. data is shifted serially into the spi shift register during the transfer and is transferred to the parallel spi data register after the last bit is shifted in. after the 16th (last) sck edge: data that was previously in the master spi data register should now be in the slave data register and the data that was in the slave data register should be in the master. the spif ?g in the spi status register is set indicating that the transfer is complete. figure 11-9 is a timing diagram of an spi transfer where cpha = 0. sck waveforms are shown for cpol = 0 and cpol = 1. the diagram may be interpreted as a master or slave timing diagram because the sck, miso, and mosi pins are connected directly between the master and the slave. the miso signal is the output from the slave and the mosi signal is the output from the master. the ss pin of the master must be either high or recon?ured as a general-purpose output not affecting the spi. figure 11-9. spi clock format 0 (cpha = 0) in slave mode, if the ss line is not deasserted between the successive transmissions then the content of the spi data register is not transmitted, instead the last received byte is transmitted. if the ss line is deasserted for at least minimum idle time (half sck cycle) between successive transmissions then the content of the spi data register is transmitted. tl begin end sck (cpol = 0) sample i change o sel ss (o) transfer sck (cpol = 1) msb ?st (lsbfe = 0): lsb ?st (lsbfe = 1): msb lsb lsb msb bit 5 bit 2 bit 6 bit 1 bit 4 bit 3 bit 3 bit 4 bit 2 bit 5 bit 1 bit 6 change o sel ss (i) mosi pin miso pin master only mosi/miso tt if next transfer begins here for t t , t l , t l minimum 1/2 sck ti tl t l = minimum leading time before the ?st sck edge t t = minimum trailing time after the last sck edge t i = minimum idling time between transfers (minimum ss high time) t l , t t , and t i are guaranteed for the master mode and required for the slave mode. 1 2 34 56 78910111213141516 sck edge nr. end of idle state begin of idle state chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 372 freescale semiconductor in master mode, with slave select output enabled the ss line is always deasserted and reasserted between successive transfers for at least minimum idle time. 11.4.3.3 cpha = 1 transfer format some peripherals require the ?st sck edge before the ?st data bit becomes available at the data out pin, the second edge clocks data into the system. in this format, the ?st sck edge is issued by setting the cpha bit at the beginning of the 8-cycle transfer operation. the ?st edge of sck occurs immediately after the half sck clock cycle synchronization delay. this ?st edge commands the slave to transfer its ?st data bit to the serial data input pin of the master. a half sck cycle later, the second edge appears on the sck pin. this is the latching edge for both the master and slave. when the third edge occurs, the value previously latched from the serial data input pin is shifted into the lsb or msb of the spi shift register, depending on lsbfe bit. after this edge, the next bit of the master data is coupled out of the serial data output pin of the master to the serial input pin on the slave. this process continues for a total of 16 edges on the sck line with data being latched on even numbered edges and shifting taking place on odd numbered edges. data reception is double buffered, data is serially shifted into the spi shift register during the transfer and is transferred to the parallel spi data register after the last bit is shifted in. after the 16th sck edge: data that was previously in the spi data register of the master is now in the data register of the slave, and data that was in the data register of the slave is in the master. the spif ?g bit in spisr is set indicating that the transfer is complete. figure 11-10 shows two clocking variations for cpha = 1. the diagram may be interpreted as a master or slave timing diagram because the sck, miso, and mosi pins are connected directly between the master and the slave. the miso signal is the output from the slave, and the mosi signal is the output from the master. the ss line is the slave select input to the slave. the ss pin of the master must be either high or recon?ured as a general-purpose output not affecting the spi. the ss line can remain active low between successive transfers (can be tied low at all times). this format is sometimes preferred in systems having a single ?ed master and a single slave that drive the miso data line. back-to-back transfers in master mode in master mode, if a transmission has completed and a new data byte is available in the spi data register, this byte is send out immediately without a trailing and minimum idle time. the spi interrupt request ?g (spif) is common to both the master and slave modes. spif gets set one half sck cycle after the last sck edge. chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 373 figure 11-10. spi clock format 1 (cpha = 1) 11.4.4 spi baud rate generation baud rate generation consists of a series of divider stages. six bits in the spi baud rate register (sppr2, sppr1, sppr0, spr2, spr1, and spr0) determine the divisor to the spi module clock which results in the spi baud rate. the spi clock rate is determined by the product of the value in the baud rate preselection bits (sppr2?ppr0) and the value in the baud rate selection bits (spr2?pr0). the module clock divisor equation is shown in figure 11-11 when all bits are clear (the default condition), the spi module clock is divided by 2. when the selection bits (spr2?pr0) are 001 and the preselection bits (sppr2?ppr0) are 000, the module clock divisor becomes 4. when the selection bits are 010, the module clock divisor becomes 8 etc. when the preselection bits are 001, the divisor determined by the selection bits is multiplied by 2. when the preselection bits are 010, the divisor is multiplied by 3, etc. see table 11-7 for baud rate calculations for all bit conditions, based on a 25-mhz bus clock. the two sets of selects allows the clock to be divided by a non-power of two to achieve other baud rates such as divide by 6, divide by 10, etc. tl tt for t t , t l , t l minimum 1/2 sck ti tl if next transfer begins here begin end sck (cpol = 0) sample i change o sel ss (o) transfer sck (cpol = 1) msb ?st (lsbfe = 0): lsb ?st (lsbfe = 1): msb lsb lsb msb bit 5 bit 2 bit 6 bit 1 bit 4 bit 3 bit 3 bit 4 bit 2 bit 5 bit 1 bit 6 change o sel ss (i) mosi pin miso pin master only mosi/miso t l = minimum leading time before the ?st sck edge, not required for back to back transfers t t = minimum trailing time after the last sck edge t i = minimum idling time between transfers (minimum ss high time), not required for back to back transfers 1 2 34 56 78910111213141516 sck edge nr. end of idle state begin of idle state chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 374 freescale semiconductor the baud rate generator is activated only when the spi is in the master mode and a serial transfer is taking place. in the other cases, the divider is disabled to decrease i dd current. figure 11-11. baud rate divisor equation 11.4.5 special features 11.4.5.1 ss output the ss output feature automatically drives the ss pin low during transmission to select external devices and drives it high during idle to deselect external devices. when ss output is selected, the ss output pin is connected to the ss input pin of the external device. the ss output is available only in master mode during normal spi operation by asserting ssoe and modfen bit as shown in table 11-3 . the mode fault feature is disabled while ss output is enabled. note care must be taken when using the ss output feature in a multimaster system because the mode fault feature is not available for detecting system errors between masters. 11.4.5.2 bidirectional mode (mosi or miso) the bidirectional mode is selected when the spc0 bit is set in spi control register 2 (see table 11-9 ). in this mode, the spi uses only one serial data pin for the interface with external device(s). the mstr bit decides which pin to use. the mosi pin becomes the serial data i/o (momi) pin for the master mode, and the miso pin becomes serial data i/o (siso) pin for the slave mode. the miso pin in master mode and mosi pin in slave mode are not used by the spi. table 11-9. normal mode and bidirectional mode when spe = 1 master mode mstr = 1 slave mode mstr = 0 normal mode spc0 = 0 bidirectional mode spc0 = 1 baudratedivisor sppr 1 + () 2 ? spr 1 + () = spi mosi miso serial out serial in spi mosi miso serial in serial out spi momi serial out serial in bidiroe spi siso serial in serial out bidiroe chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 375 the direction of each serial i/o pin depends on the bidiroe bit. if the pin is con?ured as an output, serial data from the shift register is driven out on the pin. the same pin is also the serial input to the shift register. the sck is output for the master mode and input for the slave mode. the ss is the input or output for the master mode, and it is always the input for the slave mode. the bidirectional mode does not affect sck and ss functions. note in bidirectional master mode, with mode fault enabled, both data pins miso and mosi can be occupied by the spi, though mosi is normally used for transmissions in bidirectional mode and miso is not used by the spi. if a mode fault occurs, the spi is automatically switched to slave mode, in this case miso becomes occupied by the spi and mosi is not used. this has to be considered, if the miso pin is used for other purpose. 11.4.6 error conditions the spi has one error condition: mode fault error 11.4.6.1 mode fault error if the ss input becomes low while the spi is con?ured as a master, it indicates a system error where more than one master may be trying to drive the mosi and sck lines simultaneously. this condition is not permitted in normal operation, the modf bit in the spi status register is set automatically provided the modfen bit is set. in the special case where the spi is in master mode and modfen bit is cleared, the ss pin is not used by the spi. in this special case, the mode fault error function is inhibited and modf remains cleared. in case the spi system is con?ured as a slave, the ss pin is a dedicated input pin. mode fault error doesn t occur in slave mode. if a mode fault error occurs the spi is switched to slave mode, with the exception that the slave output buffer is disabled. so sck, miso and mosi pins are forced to be high impedance inputs to avoid any possibility of con?ct with another output driver. a transmission in progress is aborted and the spi is forced into idle state. if the mode fault error occurs in the bidirectional mode for a spi system con?ured in master mode, output enable of the momi (mosi in bidirectional mode) is cleared if it was set. no mode fault error occurs in the bidirectional mode for spi system con?ured in slave mode. the mode fault ?g is cleared automatically by a read of the spi status register (with modf set) followed by a write to spi control register 1. if the mode fault ?g is cleared, the spi becomes a normal master or slave again. chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 376 freescale semiconductor 11.4.7 operation in run mode in run mode with the spi system enable (spe) bit in the spi control register clear, the spi system is in a low-power, disabled state. spi registers remain accessible, but clocks to the core of this module are disabled. 11.4.8 operation in wait mode spi operation in wait mode depends upon the state of the spiswai bit in spi control register 2. if spiswai is clear, the spi operates normally when the cpu is in wait mode if spiswai is set, spi clock generation ceases and the spi module enters a power conservation state when the cpu is in wait mode. if spiswai is set and the spi is con?ured for master, any transmission and reception in progress stops at wait mode entry. the transmission and reception resumes when the spi exits wait mode. if spiswai is set and the spi is con?ured as a slave, any transmission and reception in progress continues if the sck continues to be driven from the master. this keeps the slave synchronized to the master and the sck. if the master transmits several bytes while the slave is in wait mode, the slave will continue to send out bytes consistent with the operation mode at the start of wait mode (i.e. if the slave is currently sending its spidr to the master, it will continue to send the same byte. else if the slave is currently sending the last received byte from the master, it will continue to send each previous master byte). note care must be taken when expecting data from a master while the slave is in wait or stop mode. even though the shift register will continue to operate, the rest of the spi is shut down (i.e. a spif interrupt will not be generated until exiting stop or wait mode). also, the byte from the shift register will not be copied into the spidr register until after the slave spi has exited wait or stop mode. a spif ?g and spidr copy is only generated if wait mode is entered or exited during a tranmission. if the slave enters wait mode in idle mode and exits wait mode in idle mode, neither a spif nor a spidr copy will occur. 11.4.9 operation in stop mode stop mode is dependent on the system. the spi enters stop mode when the module clock is disabled (held high or low). if the spi is in master mode and exchanging data when the cpu enters stop mode, the transmission is frozen until the cpu exits stop mode. after stop, data to and from the external spi is exchanged correctly. in slave mode, the spi will stay synchronized with the master. the stop mode is not dependent on the spiswai bit. chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 377 11.5 reset the reset values of registers and signals are described in the memory map and registers section (see section 11.3, ?emory map and register de?ition ) which details the registers and their bit-?lds. if a data transmission occurs in slave mode after reset without a write to spidr, it will transmit garbage, or the byte last received from the master before the reset. reading from the spidr after reset will always read a byte of zeros. 11.6 interrupts the spi only originates interrupt requests when spi is enabled (spe bit in spicr1 set). the following is a description of how the spi makes a request and how the mcu should acknowledge that request. the interrupt vector offset and interrupt priority are chip dependent. the interrupt ?gs modf, spif and sptef are logically ored to generate an interrupt request. 11.6.1 modf modf occurs when the master detects an error on the ss pin. the master spi must be con?ured for the modf feature (see table 11-3 ). after modf is set, the current transfer is aborted and the following bit is changed: mstr = 0, the master bit in spicr1 resets. the modf interrupt is re?cted in the status register modf ?g. clearing the ?g will also clear the interrupt. this interrupt will stay active while the modf ?g is set. modf has an automatic clearing process which is described in section 11.3.2.4, ?pi status register (spisr) . 11.6.2 spif spif occurs when new data has been received and copied to the spi data register. after spif is set, it does not clear until it is serviced. spif has an automatic clearing process which is described in section 11.3.2.4, ?pi status register (spisr) . in the event that the spif is not serviced before the end of the next transfer (i.e. spif remains active throughout another transfer), the latter transfers will be ignored and no new data will be copied into the spidr. 11.6.3 sptef sptef occurs when the spi data register is ready to accept new data. after sptef is set, it does not clear until it is serviced. sptef has an automatic clearing process which is described in section 11.3.2.4, ?pi status register (spisr) . chapter 11 serial peripheral interface (spiv3) mc9s12kg128 data sheet, rev. 1.15 378 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 379 chapter 12 pulse-width modulator (pwm8b8cv1) 12.1 introduction the pwm de?ition is based on the hc12 pwm de?itions. it contains the basic features from the hc11 with some of the enhancements incorporated on the hc12: center aligned output mode and four available clock sources.the pwm module has eight channels with independent control of left and center aligned outputs on each channel. each of the eight channels has a programmable period and duty cycle as well as a dedicated counter. a ?xible clock select scheme allows a total of four different clock sources to be used with the counters. each of the modulators can create independent continuous waveforms with software-selectable duty rates from 0% to 100%. the pwm outputs can be programmed as left aligned outputs or center aligned outputs. 12.1.1 features the pwm block includes these distinctive features: eight independent pwm channels with programmable period and duty cycle dedicated counter for each pwm channel programmable pwm enable/disable for each channel software selection of pwm duty pulse polarity for each channel period and duty cycle are double buffered. change takes effect when the end of the effective period is reached (pwm counter reaches zero) or when the channel is disabled. programmable center or left aligned outputs on individual channels eight 8-bit channel or four 16-bit channel pwm resolution four clock sources (a, b, sa, and sb) provide for a wide range of frequencies programmable clock select logic emergency shutdown 12.1.2 modes of operation there is a software programmable option for low power consumption in wait mode that disables the input clock to the prescaler. in freeze mode there is a software programmable option to disable the input clock to the prescaler. this is useful for emulation. chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 380 freescale semiconductor 12.1.3 block diagram figure 12-1 shows the block diagram for the 8-bit 8-channel pwm block. figure 12-1. pwm block diagram 12.2 external signal description the pwm module has a total of 8 external pins. 12.2.1 pwm7 ?pwm channel 7 this pin serves as waveform output of pwm channel 7 and as an input for the emergency shutdown feature. 12.2.2 pwm6 ?pwm channel 6 this pin serves as waveform output of pwm channel 6. period and duty counter channel 6 clock select pwm clock period and duty counter channel 5 period and duty counter channel 4 period and duty counter channel 3 period and duty counter channel 2 period and duty counter channel 1 alignment polarity control pwm8b8c pwm6 pwm5 pwm4 pwm3 pwm2 pwm1 enable pwm channels period and duty counter channel 7 period and duty counter channel 0 pwm0 pwm7 bus clock chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 381 12.2.3 pwm5 ?pwm channel 5 this pin serves as waveform output of pwm channel 5. 12.2.4 pwm4 ?pwm channel 4 this pin serves as waveform output of pwm channel 4. 12.2.5 pwm3 ?pwm channel 3 this pin serves as waveform output of pwm channel 3. 12.2.6 pwm3 ?pwm channel 2 this pin serves as waveform output of pwm channel 2. 12.2.7 pwm3 ?pwm channel 1 this pin serves as waveform output of pwm channel 1. 12.2.8 pwm3 ?pwm channel 0 this pin serves as waveform output of pwm channel 0. 12.3 memory map and register de?ition this section describes in detail all the registers and register bits in the pwm module. the special-purpose registers and register bit functions that are not normally available to device end users, such as factory test control registers and reserved registers, are clearly identi?d by means of shading the appropriate portions of address maps and register diagrams. notes explaining the reasons for restricting access to the registers and functions are also explained in the individual register descriptions. 12.3.1 module memory map this section describes the content of the registers in the pwm module. the base address of the pwm module is determined at the mcu level when the mcu is de?ed. the register decode map is ?ed and begins at the ?st address of the module address offset. the ?ure below shows the registers associated with the pwm and their relative offset from the base address. the register detail description follows the order they appear in the register map. reserved bits within a register will always read as 0 and the write will be unimplemented. unimplemented functions are indicated by shading the bit. . chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 382 freescale semiconductor note register address = base address + address offset, where the base address is de?ed at the mcu level and the address offset is de?ed at the module level. 12.3.2 register descriptions this section describes in detail all the registers and register bits in the pwm module. register name bit 7 6 5 4 3 2 1 bit 0 pwme r pwme7 pwme6 pwme5 pwme4 pwme3 pwme2 pwme1 pwme0 w pwmpol r ppol7 ppol6 ppol5 ppol4 ppol3 ppol2 ppol1 ppol0 w pwmclk r pclk7 pclkl6 pclk5 pclk4 pclk3 pclk2 pclk1 pclk0 w pwmprclk r 0 pckb2 pckb1 pckb0 0 pcka2 pcka1 pcka0 w pwmcae r cae7 cae6 cae5 cae4 cae3 cae2 cae1 cae0 w pwmctl r con67 con45 con23 con01 pswai pfrz 00 w pwmtst 1 r00 0 00000 w pwmprsc 1 r00 0 00000 w pwmscla r bit 7 6 5 4 3 2 1 bit 0 w pwmsclb r bit 7 6 5 4 3 2 1 bit 0 w pwmscnta 1 r00 0 00000 w pwmscntb 1 r00 0 00000 w = unimplemented or reserved figure 12-2. pwm register summary (sheet 1 of 3) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 383 pwmcnt0 r bit 7 6 5 4 3 2 1 bit 0 w00 0 00000 pwmcnt1 r bit 7 6 5 4 3 2 1 bit 0 w00 0 00000 pwmcnt2 r bit 7 6 5 4 3 2 1 bit 0 w00 0 00000 pwmcnt3 r bit 7 6 5 4 3 2 1 bit 0 w00 0 00000 pwmcnt4 r bit 7 6 5 4 3 2 1 bit 0 w00 0 00000 pwmcnt5 r bit 7 6 5 4 3 2 1 bit 0 w00 0 00000 pwmcnt6 r bit 7 6 5 4 3 2 1 bit 0 w00 0 00000 pwmcnt7 r bit 7 6 5 4 3 2 1 bit 0 w00 0 00000 pwmper0 r bit 7 6 5 4 3 2 1 bit 0 w pwmper1 r bit 7 6 5 4 3 2 1 bit 0 w pwmper2 r bit 7 6 5 4 3 2 1 bit 0 w pwmper3 r bit 7 6 5 4 3 2 1 bit 0 w pwmper4 r bit 7 6 5 4 3 2 1 bit 0 w pwmper5 r bit 7 6 5 4 3 2 1 bit 0 w pwmper6 r bit 7 6 5 4 3 2 1 bit 0 w register name bit 7 6 5 4 3 2 1 bit 0 = unimplemented or reserved figure 12-2. pwm register summary (sheet 2 of 3) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 384 freescale semiconductor 12.3.2.1 pwm enable register (pwme) each pwm channel has an enable bit (pwmex) to start its waveform output. when any of the pwmex bits are set (pwmex = 1), the associated pwm output is enabled immediately. however, the actual pwm waveform is not available on the associated pwm output until its clock source begins its next cycle due to the synchronization of pwmex and the clock source. note the ?st pwm cycle after enabling the channel can be irregular. an exception to this is when channels are concatenated. once concatenated mode is enabled (conxx bits set in pwmctl register), enabling/disabling the corresponding 16-bit pwm channel is controlled by the pwmper7 r bit 7 6 5 4 3 2 1 bit 0 w pwmdty0 r bit 7 6 5 4 3 2 1 bit 0 w pwmdty1 r bit 7 6 5 4 3 2 1 bit 0 w pwmdty2 r bit 7 6 5 4 3 2 1 bit 0 w pwmdty3 r bit 7 6 5 4 3 2 1 bit 0 w pwmdty4 r bit 7 6 5 4 3 2 1 bit 0 w pwmdty5 r bit 7 6 5 4 3 2 1 bit 0 w pwmdty6 r bit 7 6 5 4 3 2 1 bit 0 w pwmdty7 r bit 7 6 5 4 3 2 1 bit 0 w pwmsdn r pwmif pwmie 0 pwmlvl 0 pwm7in pwm7inl pwm7ena w pwmrstrt 1 intended for factory test purposes only. register name bit 7 6 5 4 3 2 1 bit 0 = unimplemented or reserved figure 12-2. pwm register summary (sheet 3 of 3) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 385 low order pwmex bit.in this case, the high order bytes pwmex bits have no effect and their corresponding pwm output lines are disabled. while in run mode, if all eight pwm channels are disabled (pwme7? = 0), the prescaler counter shuts off for power savings. read: anytime write: anytime 76543210 r pwme7 pwme6 pwme5 pwme4 pwme3 pwme2 pwme1 pwme0 w reset 0 0 0 00000 figure 12-3. pwm enable register (pwme) table 12-1. pwme field descriptions field description 7 pwme7 pulse width channel 7 enable 0 pulse width channel 7 is disabled. 1 pulse width channel 7 is enabled. the pulse modulated signal becomes available at pwm output bit 7 when its clock source begins its next cycle. 6 pwme6 pulse width channel 6 enable 0 pulse width channel 6 is disabled. 1 pulse width channel 6 is enabled. the pulse modulated signal becomes available at pwm output bit6 when its clock source begins its next cycle. if con67=1, then bit has no effect and pwm output line 6 is disabled. 5 pwme5 pulse width channel 5 enable 0 pulse width channel 5 is disabled. 1 pulse width channel 5 is enabled. the pulse modulated signal becomes available at pwm output bit 5 when its clock source begins its next cycle. 4 pwme4 pulse width channel 4 enable 0 pulse width channel 4 is disabled. 1 pulse width channel 4 is enabled. the pulse modulated signal becomes available at pwm, output bit 4 when its clock source begins its next cycle. if con45 = 1, then bit has no effect and pwm output bit4 is disabled. 3 pwme3 pulse width channel 3 enable 0 pulse width channel 3 is disabled. 1 pulse width channel 3 is enabled. the pulse modulated signal becomes available at pwm, output bit 3 when its clock source begins its next cycle. 2 pwme2 pulse width channel 2 enable 0 pulse width channel 2 is disabled. 1 pulse width channel 2 is enabled. the pulse modulated signal becomes available at pwm, output bit 2 when its clock source begins its next cycle. if con23 = 1, then bit has no effect and pwm output bit2 is disabled. 1 pwme1 pulse width channel 1 enable 0 pulse width channel 1 is disabled. 1 pulse width channel 1 is enabled. the pulse modulated signal becomes available at pwm, output bit 1 when its clock source begins its next cycle. 0 pwme0 pulse width channel 0 enable 0 pulse width channel 0 is disabled. 1 pulse width channel 0 is enabled. the pulse modulated signal becomes available at pwm, output bit 0 when its clock source begins its next cycle. if con01 = 1, then bit has no effect and pwm output line0 is disabled. chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 386 freescale semiconductor 12.3.2.2 pwm polarity register (pwmpol) the starting polarity of each pwm channel waveform is determined by the associated ppolx bit in the pwmpol register. if the polarity bit is one, the pwm channel output is high at the beginning of the cycle and then goes low when the duty count is reached. conversely, if the polarity bit is zero, the output starts low and then goes high when the duty count is reached. read: anytime write: anytime note ppolx register bits can be written anytime. if the polarity is changed while a pwm signal is being generated, a truncated or stretched pulse can occur during the transition 12.3.2.3 pwm clock select register (pwmclk) each pwm channel has a choice of two clocks to use as the clock source for that channel as described below. read: anytime write: anytime 76543210 r ppol7 ppol6 ppol5 ppol4 ppol3 ppol2 ppol1 ppol0 w reset 0 0 0 00000 figure 12-4. pwm polarity register (pwmpol) table 12-2. pwmpol field descriptions field description 7? ppol[7:0] p ulse width channel 7? polarity bits 0 pwm channel 7? outputs are low at the beginning of the period, then go high when the duty count is reached. 1 pwm channel 7? outputs are high at the beginning of the period, then go low when the duty count is reached. 76543210 r pclk7 pclkl6 pclk5 pclk4 pclk3 pclk2 pclk1 pclk0 w reset 0 0 0 00000 figure 12-5. pwm clock select register (pwmclk) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 387 note register bits pclk0 to pclk7 can be written anytime. if a clock select is changed while a pwm signal is being generated, a truncated or stretched pulse can occur during the transition. 12.3.2.4 pwm prescale clock select register (pwmprclk) this register selects the prescale clock source for clocks a and b independently. read: anytime write: anytime table 12-3. pwmclk field descriptions field description 7 pclk7 pulse width channel 7 clock select 0 clock b is the clock source for pwm channel 7. 1 clock sb is the clock source for pwm channel 7. 6 pclk6 pulse width channel 6 clock select 0 clock b is the clock source for pwm channel 6. 1 clock sb is the clock source for pwm channel 6. 5 pclk5 pulse width channel 5 clock select 0 clock a is the clock source for pwm channel 5. 1 clock sa is the clock source for pwm channel 5. 4 pclk4 pulse width channel 4 clock select 0 clock a is the clock source for pwm channel 4. 1 clock sa is the clock source for pwm channel 4. 3 pclk3 pulse width channel 3 clock select 0 clock b is the clock source for pwm channel 3. 1 clock sb is the clock source for pwm channel 3. 2 pclk2 pulse width channel 2 clock select 0 clock b is the clock source for pwm channel 2. 1 clock sb is the clock source for pwm channel 2. 1 pclk1 pulse width channel 1 clock select 0 clock a is the clock source for pwm channel 1. 1 clock sa is the clock source for pwm channel 1. 0 pclk0 pulse width channel 0 clock select 0 clock a is the clock source for pwm channel 0. 1 clock sa is the clock source for pwm channel 0. 76543210 r0 pckb2 pckb1 pckb0 0 pcka2 pcka1 pcka0 w reset 0 0 0 00000 = unimplemented or reserved figure 12-6. pwm prescale clock select register (pwmprclk) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 388 freescale semiconductor note pckb2? and pcka2? register bits can be written anytime. if the clock pre-scale is changed while a pwm signal is being generated, a truncated or stretched pulse can occur during the transition. s 12.3.2.5 pwm center align enable register (pwmcae) the pwmcae register contains eight control bits for the selection of center aligned outputs or left aligned outputs for each pwm channel. if the caex bit is set to a one, the corresponding pwm output will be center aligned. if the caex bit is cleared, the corresponding pwm output will be left aligned. see section 12.4.2.5, ?eft aligned outputs and section 12.4.2.6, ?enter aligned outputs for a more detailed description of the pwm output modes. table 12-4. pwmprclk field descriptions field description 6? pckb[2:0] prescaler select for clock b clock b is one of two clock sources which can be used for channels 2, 3, 6, or 7. these three bits determine the rate of clock b, as shown in table 12-5 . 2? pcka[2:0] prescaler select for clock a clock a is one of two clock sources which can be used for channels 0, 1, 4 or 5. these three bits determine the rate of clock a, as shown in table 12-6 . table 12-5. clock b prescaler selects pckb2 pckb1 pckb0 value of clock b 0 0 0 bus clock 0 0 1 bus clock / 2 0 1 0 bus clock / 4 0 1 1 bus clock / 8 1 0 0 bus clock / 16 1 0 1 bus clock / 32 1 1 0 bus clock / 64 1 1 1 bus clock / 128 table 12-6. clock a prescaler selects pcka2 pcka1 pcka0 value of clock a 0 0 0 bus clock 0 0 1 bus clock / 2 0 1 0 bus clock / 4 0 1 1 bus clock / 8 1 0 0 bus clock / 16 1 0 1 bus clock / 32 1 1 0 bus clock / 64 1 1 1 bus clock / 128 76543210 r cae7 cae6 cae5 cae4 cae3 cae2 cae1 cae0 w reset 0 0 0 00000 figure 12-7. pwm center align enable register (pwmcae) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 389 read: anytime write: anytime note write these bits only when the corresponding channel is disabled. 12.3.2.6 pwm control register (pwmctl) the pwmctl register provides for various control of the pwm module. read: anytime write: anytime there are three control bits for concatenation, each of which is used to concatenate a pair of pwm channels into one 16-bit channel. when channels 6 and 7are concatenated, channel 6 registers become the high order bytes of the double byte channel. when channels 4 and 5 are concatenated, channel 4 registers become the high order bytes of the double byte channel. when channels 2 and 3 are concatenated, channel 2 registers become the high order bytes of the double byte channel. when channels 0 and 1 are concatenated, channel 0 registers become the high order bytes of the double byte channel. see section 12.4.2.7, ?wm 16-bit functions for a more detailed description of the concatenation pwm function. note change these bits only when both corresponding channels are disabled. table 12-7. pwmcae field descriptions field description 7? cae[7:0] center aligned output modes on channels 7? 0 channels 7? operate in left aligned output mode. 1 channels 7? operate in center aligned output mode. 76543210 r con67 con45 con23 con01 pswai pfrz 00 w reset 0 0 0 00000 = unimplemented or reserved figure 12-8. pwm control register (pwmctl) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 390 freescale semiconductor 12.3.2.7 reserved register (pwmtst) this register is reserved for factory testing of the pwm module and is not available in normal modes. table 12-8. pwmctl field descriptions field description 7 con67 concatenate channels 6 and 7 0 channels 6 and 7 are separate 8-bit pwms. 1 channels 6 and 7 are concatenated to create one 16-bit pwm channel. channel 6 becomes the high order byte and channel 7 becomes the low order byte. channel 7 output pin is used as the output for this 16-bit pwm (bit 7 of port pwmp). channel 7 clock select control-bit determines the clock source, channel 7 polarity bit determines the polarity, channel 7 enable bit enables the output and channel 7 center aligned enable bit determines the output mode. 6 con45 concatenate channels 4 and 5 0 channels 4 and 5 are separate 8-bit pwms. 1 channels 4 and 5 are concatenated to create one 16-bit pwm channel. channel 4 becomes the high order byte and channel 5 becomes the low order byte. channel 5 output pin is used as the output for this 16-bit pwm (bit 5 of port pwmp). channel 5 clock select control-bit determines the clock source, channel 5 polarity bit determines the polarity, channel 5 enable bit enables the output and channel 5 center aligned enable bit determines the output mode. 5 con23 concatenate channels 2 and 3 0 channels 2 and 3 are separate 8-bit pwms. 1 channels 2 and 3 are concatenated to create one 16-bit pwm channel. channel 2 becomes the high order byte and channel 3 becomes the low order byte. channel 3 output pin is used as the output for this 16-bit pwm (bit 3 of port pwmp). channel 3 clock select control-bit determines the clock source, channel 3 polarity bit determines the polarity, channel 3 enable bit enables the output and channel 3 center aligned enable bit determines the output mode. 4 con01 concatenate channels 0 and 1 0 channels 0 and 1 are separate 8-bit pwms. 1 channels 0 and 1 are concatenated to create one 16-bit pwm channel. channel 0 becomes the high order byte and channel 1 becomes the low order byte. channel 1 output pin is used as the output for this 16-bit pwm (bit 1 of port pwmp). channel 1 clock select control-bit determines the clock source, channel 1 polarity bit determines the polarity, channel 1 enable bit enables the output and channel 1 center aligned enable bit determines the output mode. 3 pswai pwm stops in wait mode enabling this bit allows for lower power consumption in wait mode by disabling the input clock to the prescaler. 0 allow the clock to the prescaler to continue while in wait mode. 1 stop the input clock to the prescaler whenever the mcu is in wait mode. 2 pfrez pwm counters stop in freeze mode ?in freeze mode, there is an option to disable the input clock to the prescaler by setting the pfrz bit in the pwmctl register. if this bit is set, whenever the mcu is in freeze mode, the input clock to the prescaler is disabled. this feature is useful during emulation as it allows the pwm function to be suspended. in this way, the counters of the pwm can be stopped while in freeze mode so that once normal program ow is continued, the counters are re-enabled to simulate real-time operations. since the registers can still be accessed in this mode, to re-enable the prescaler clock, either disable the pfrz bit or exit freeze mode. 0 allow pwm to continue while in freeze mode. 1 disable pwm input clock to the prescaler whenever the part is in freeze mode. this is useful for emulation. chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 391 read: always read $00 in normal modes write: unimplemented in normal modes note writing to this register when in special modes can alter the pwm functionality. 12.3.2.8 reserved register (pwmprsc) this register is reserved for factory testing of the pwm module and is not available in normal modes. read: always read $00 in normal modes write: unimplemented in normal modes note writing to this register when in special modes can alter the pwm functionality. 12.3.2.9 pwm scale a register (pwmscla) pwmscla is the programmable scale value used in scaling clock a to generate clock sa. clock sa is generated by taking clock a, dividing it by the value in the pwmscla register and dividing that by two. clock sa = clock a / (2 * pwmscla) note when pwmscla = $00, pwmscla value is considered a full scale value of 256. clock a is thus divided by 512. any value written to this register will cause the scale counter to load the new scale value (pwmscla). 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 12-9. reserved register (pwmtst) 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 12-10. reserved register (pwmprsc) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 392 freescale semiconductor read: anytime write: anytime (causes the scale counter to load the pwmscla value) 12.3.2.10 pwm scale b register (pwmsclb) pwmsclb is the programmable scale value used in scaling clock b to generate clock sb. clock sb is generated by taking clock b, dividing it by the value in the pwmsclb register and dividing that by two. clock sb = clock b / (2 * pwmsclb) note when pwmsclb = $00, pwmsclb value is considered a full scale value of 256. clock b is thus divided by 512. any value written to this register will cause the scale counter to load the new scale value (pwmsclb). read: anytime write: anytime (causes the scale counter to load the pwmsclb value). 12.3.2.11 reserved registers (pwmscntx) the registers pwmscnta and pwmscntb are reserved for factory testing of the pwm module and are not available in normal modes. read: always read $00 in normal modes write: unimplemented in normal modes 76543210 r bit 7 6 5 4 3 2 1 bit 0 w reset 0 0 0 00000 figure 12-11. pwm scale a register (pwmscla) 76543210 r bit 7 6 5 4 3 2 1 bit 0 w reset 0 0 0 00000 figure 12-12. pwm scale b register (pwmsclb) 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 12-13. reserved registers (pwmscntx) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 393 note writing to these registers when in special modes can alter the pwm functionality. 12.3.2.12 pwm channel counter registers (pwmcntx) each channel has a dedicated 8-bit up/down counter which runs at the rate of the selected clock source. the counter can be read at any time without affecting the count or the operation of the pwm channel. in left aligned output mode, the counter counts from 0 to the value in the period register - 1. in center aligned output mode, the counter counts from 0 up to the value in the period register and then back down to 0. any value written to the counter causes the counter to reset to $00, the counter direction to be set to up, the immediate load of both duty and period registers with values from the buffers, and the output to change according to the polarity bit. the counter is also cleared at the end of the effective period (see section 12.4.2.5, ?eft aligned outputs and section 12.4.2.6, ?enter aligned outputs for more details). when the channel is disabled (pwmex = 0), the pwmcntx register does not count. when a channel becomes enabled (pwmex = 1), the associated pwm counter starts at the count in the pwmcntx register. for more detailed information on the operation of the counters, see section 12.4.2.4, ?wm timer counters . in concatenated mode, writes to the 16-bit counter by using a 16-bit access or writes to either the low or high order byte of the counter will reset the 16-bit counter. reads of the 16-bit counter must be made by 16-bit access to maintain data coherency. note writing to the counter while the channel is enabled can cause an irregular pwm cycle to occur. read: anytime write: anytime (any value written causes pwm counter to be reset to $00). 12.3.2.13 pwm channel period registers (pwmperx) there is a dedicated period register for each channel. the value in this register determines the period of the associated pwm channel. the period registers for each channel are double buffered so that if they change while the channel is enabled, the change will not take effect until one of the following occurs: the effective period ends the counter is written (counter resets to $00) the channel is disabled 76543210 r bit 7 6 5 4 3 2 1 bit 0 w00000000 reset 0 0 0 00000 figure 12-14. pwm channel counter registers (pwmcntx) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 394 freescale semiconductor in this way, the output of the pwm will always be either the old waveform or the new waveform, not some variation in between. if the channel is not enabled, then writes to the period register will go directly to the latches as well as the buffer. note reads of this register return the most recent value written. reads do not necessarily return the value of the currently active period due to the double buffering scheme. see section 12.4.2.3, ?wm period and duty for more information. to calculate the output period, take the selected clock source period for the channel of interest (a, b, sa, or sb) and multiply it by the value in the period register for that channel: left aligned output (caex = 0) pwmx period = channel clock period * pwmperx center aligned output (caex = 1) pwmx period = channel clock period * (2 * pwmperx) for boundary case programming values, please refer to section 12.4.2.8, ?wm boundary cases . read: anytime write: anytime 12.3.2.14 pwm channel duty registers (pwmdtyx) there is a dedicated duty register for each channel. the value in this register determines the duty of the associated pwm channel. the duty value is compared to the counter and if it is equal to the counter value a match occurs and the output changes state. the duty registers for each channel are double buffered so that if they change while the channel is enabled, the change will not take effect until one of the following occurs: the effective period ends the counter is written (counter resets to $00) the channel is disabled in this way, the output of the pwm will always be either the old duty waveform or the new duty waveform, not some variation in between. if the channel is not enabled, then writes to the duty register will go directly to the latches as well as the buffer. 76543210 r bit 7 6 5 4 3 2 1 bit 0 w reset 1 1 1 11111 figure 12-15. pwm channel period registers (pwmperx) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 395 note reads of this register return the most recent value written. reads do not necessarily return the value of the currently active duty due to the double buffering scheme. see section 12.4.2.3, ?wm period and duty for more information. note depending on the polarity bit, the duty registers will contain the count of either the high time or the low time. if the polarity bit is one, the output starts high and then goes low when the duty count is reached, so the duty registers contain a count of the high time. if the polarity bit is zero, the output starts low and then goes high when the duty count is reached, so the duty registers contain a count of the low time. to calculate the output duty cycle (high time as a% of period) for a particular channel: polarity = 0 (ppol x =0) duty cycle = [(pwmperx-pwmdtyx)/pwmperx] * 100% polarity = 1 (ppolx = 1) duty cycle = [pwmdtyx / pwmperx] * 100% for boundary case programming values, please refer to section 12.4.2.8, ?wm boundary cases . read: anytime write: anytime 12.3.2.15 pwm shutdown register (pwmsdn) the pwmsdn register provides for the shutdown functionality of the pwm module in the emergency cases. for proper operation, channel 7 must be driven to the active level for a minimum of two bus clocks. read: anytime write: anytime 76543210 r bit 7 6 5 4 3 2 1 bit 0 w reset 1 1 1 11111 figure 12-16. pwm channel duty registers (pwmdtyx) 76543210 r pwmif pwmie 0 pwmlvl 0 pwm7in pwm7inl pwm7ena w pwmrstrt reset 0 0 0 00000 = unimplemented or reserved figure 12-17. pwm shutdown register (pwmsdn) chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 396 freescale semiconductor 12.4 functional description 12.4.1 pwm clock select there are four available clocks: clock a, clock b, clock sa (scaled a), and clock sb (scaled b). these four clocks are based on the bus clock. clock a and b can be software selected to be 1, 1/2, 1/4, 1/8,..., 1/64, 1/128 times the bus clock. clock sa uses clock a as an input and divides it further with a reloadable counter. similarly, clock sb uses clock b as an input and divides it further with a reloadable counter. the rates available for clock sa are software selectable to be clock a divided by 2, 4, 6, 8,..., or 512 in increments of divide by 2. similar rates are available for clock sb. each pwm channel has the capability of selecting one of two clocks, either the pre-scaled clock (clock a or b) or the scaled clock (clock sa or sb). the block diagram in figure 12-18 shows the four different clocks and how the scaled clocks are created. table 12-9. pwmsdn field descriptions field description 7 pwmif pwm interrupt flag ?any change from passive to asserted (active) state or from active to passive state will be ?gged by setting the pwmif ?g = 1. the ?g is cleared by writing a logic 1 to it. writing a 0 has no effect. 0 no change on pwm7in input. 1 change on pwm7in input 6 pwmie pwm interrupt enable ?if interrupt is enabled an interrupt to the cpu is asserted. 0 pwm interrupt is disabled. 1 pwm interrupt is enabled. 5 pwmrstrt pwm restart the pwm can only be restarted if the pwm channel input 7 is de-asserted. after writing a logic 1 to the pwmrstrt bit (trigger event) the pwm channels start running after the corresponding counter passes next ?ounter == 0?phase. also, if the pwm7ena bit is reset to 0, the pwm do not start before the counter passes $00. the bit is always read as ?? 4 pwmlvl pwm shutdown output level if active level as de?ed by the pwm7in input, gets asserted all enabled pwm channels are immediately driven to the level de?ed by pwmlvl. 0 pwm outputs are forced to 0 1 outputs are forced to 1. 2 pwm7in pwm channel 7 input status ?this re?cts the current status of the pwm7 pin. 1 pwm7inl pwm shutdown active input level for channel 7 ?if the emergency shutdown feature is enabled (pwm7ena = 1), this bit determines the active level of the pwm7channel. 0 active level is low 1 active level is high 0 pwm7ena pwm emergency shutdown enable if this bit is logic 1, the pin associated with channel 7 is forced to input and the emergency shutdown feature is enabled. all the other bits in this register are meaningful only if pwm7ena = 1. 0 pwm emergency feature disabled. 1 pwm emergency feature is enabled. chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 397 12.4.1.1 prescale the input clock to the pwm prescaler is the bus clock. it can be disabled whenever the part is in freeze mode by setting the pfrz bit in the pwmctl register. if this bit is set, whenever the mcu is in freeze mode (freeze mode signal active) the input clock to the prescaler is disabled. this is useful for emulation in order to freeze the pwm. the input clock can also be disabled when all eight pwm channels are disabled (pwme7-0 = 0). this is useful for reducing power by disabling the prescale counter. clock a and clock b are scaled values of the input clock. the value is software selectable for both clock a and clock b and has options of 1, 1/2, 1/4, 1/8, 1/16, 1/32, 1/64, or 1/128 times the bus clock. the value selected for clock a is determined by the pcka2, pcka1, pcka0 bits in the pwmprclk register. the value selected for clock b is determined by the pckb2, pckb1, pckb0 bits also in the pwmprclk register. 12.4.1.2 clock scale the scaled a clock uses clock a as an input and divides it further with a user programmable value and then divides this by 2. the scaled b clock uses clock b as an input and divides it further with a user programmable value and then divides this by 2. the rates available for clock sa are software selectable to be clock a divided by 2, 4, 6, 8,..., or 512 in increments of divide by 2. similar rates are available for clock sb. chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 398 freescale semiconductor figure 12-18. pwm clock select block diagram 128 248163264 pckb2 pckb1 pckb0 m u x clock a clock b clock sa clock a/2, a/4, a/6,....a/512 prescale scale divide by pfrz freeze mode signal bus clock clock select m u x pclk0 clock to pwm ch 0 m u x pclk2 clock to pwm ch 2 m u x pclk1 clock to pwm ch 1 m u x pclk4 clock to pwm ch 4 m u x pclk5 clock to pwm ch 5 m u x pclk6 clock to pwm ch 6 m u x pclk7 clock to pwm ch 7 m u x pclk3 clock to pwm ch 3 load div 2 pwmsclb clock sb clock b/2, b/4, b/6,....b/512 m u x pcka2 pcka1 pcka0 pwme7-0 count = 1 load div 2 pwmscla count = 1 8-bit down counter 8-bit down counter prescaler taps: chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 399 clock a is used as an input to an 8-bit down counter. this down counter loads a user programmable scale value from the scale register (pwmscla). when the down counter reaches one, a pulse is output and the 8-bit counter is re-loaded. the output signal from this circuit is further divided by two. this gives a greater range with only a slight reduction in granularity. clock sa equals clock a divided by two times the value in the pwmscla register. note clock sa = clock a / (2 * pwmscla) when pwmscla = $00, pwmscla value is considered a full scale value of 256. clock a is thus divided by 512. similarly, clock b is used as an input to an 8-bit down counter followed by a divide by two producing clock sb. thus, clock sb equals clock b divided by two times the value in the pwmsclb register. note clock sb = clock b / (2 * pwmsclb) when pwmsclb = $00, pwmsclb value is considered a full scale value of 256. clock b is thus divided by 512. as an example, consider the case in which the user writes $ff into the pwmscla register. clock a for this case will be e divided by 4. a pulse will occur at a rate of once every 255x4 e cycles. passing this through the divide by two circuit produces a clock signal at an e divided by 2040 rate. similarly, a value of $01 in the pwmscla register when clock a is e divided by 4 will produce a clock at an e divided by 8 rate. writing to pwmscla or pwmsclb causes the associated 8-bit down counter to be re-loaded. otherwise, when changing rates the counter would have to count down to $01 before counting at the proper rate. forcing the associated counter to re-load the scale register value every time pwmscla or pwmsclb is written prevents this. note writing to the scale registers while channels are operating can cause irregularities in the pwm outputs. 12.4.1.3 clock select each pwm channel has the capability of selecting one of two clocks. for channels 0, 1, 4, and 5 the clock choices are clock a or clock sa. for channels 2, 3, 6, and 7 the choices are clock b or clock sb. the clock selection is done with the pclkx control bits in the pwmclk register. note changing clock control bits while channels are operating can cause irregularities in the pwm outputs. chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 400 freescale semiconductor 12.4.2 pwm channel timers the main part of the pwm module are the actual timers. each of the timer channels has a counter, a period register and a duty register (each are 8-bit). the waveform output period is controlled by a match between the period register and the value in the counter. the duty is controlled by a match between the duty register and the counter value and causes the state of the output to change during the period. the starting polarity of the output is also selectable on a per channel basis. shown below in figure 12-19 is the block diagram for the pwm timer. figure 12-19. pwm timer channel block diagram 12.4.2.1 pwm enable each pwm channel has an enable bit (pwmex) to start its waveform output. when any of the pwmex bits are set (pwmex = 1), the associated pwm output signal is enabled immediately. however, the actual pwm waveform is not available on the associated pwm output until its clock source begins its next cycle due to the synchronization of pwmex and the clock source. an exception to this is when channels are concatenated. refer to section 12.4.2.7, ?wm 16-bit functions for more detail. note the ?st pwm cycle after enabling the channel can be irregular. clock source t r q q ppolx from port pwmp data register pwmex to pin driver gate 8-bit compare = pwmdtyx 8-bit compare = pwmperx caex t r q q 8-bit counter pwmcntx m u x m u x (clock edge sync) up/down reset chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 401 on the front end of the pwm timer, the clock is enabled to the pwm circuit by the pwmex bit being high. there is an edge-synchronizing circuit to guarantee that the clock will only be enabled or disabled at an edge. when the channel is disabled (pwmex = 0), the counter for the channel does not count. 12.4.2.2 pwm polarity each channel has a polarity bit to allow starting a waveform cycle with a high or low signal. this is shown on the block diagram as a mux select of either the q output or the q output of the pwm output ?p ?p. when one of the bits in the pwmpol register is set, the associated pwm channel output is high at the beginning of the waveform, then goes low when the duty count is reached. conversely, if the polarity bit is zero, the output starts low and then goes high when the duty count is reached. 12.4.2.3 pwm period and duty dedicated period and duty registers exist for each channel and are double buffered so that if they change while the channel is enabled, the change will not take effect until one of the following occurs: the effective period ends the counter is written (counter resets to $00) the channel is disabled in this way, the output of the pwm will always be either the old waveform or the new waveform, not some variation in between. if the channel is not enabled, then writes to the period and duty registers will go directly to the latches as well as the buffer. a change in duty or period can be forced into effect ?mmediately?by writing the new value to the duty and/or period registers and then writing to the counter. this forces the counter to reset and the new duty and/or period values to be latched. in addition, since the counter is readable, it is possible to know where the count is with respect to the duty value and software can be used to make adjustments note when forcing a new period or duty into effect immediately, an irregular pwm cycle can occur. depending on the polarity bit, the duty registers will contain the count of either the high time or the low time. 12.4.2.4 pwm timer counters each channel has a dedicated 8-bit up/down counter which runs at the rate of the selected clock source (see section 12.4.1, ?wm clock select for the available clock sources and rates). the counter compares to two registers, a duty register and a period register as shown in figure 12-19 . when the pwm counter matches the duty register, the output ?p-?p changes state, causing the pwm waveform to also change state. a match between the pwm counter and the period register behaves differently depending on what output mode is selected as shown in figure 12-19 and described in section 12.4.2.5, ?eft aligned outputs and section 12.4.2.6, ?enter aligned outputs . chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 402 freescale semiconductor each channel counter can be read at anytime without affecting the count or the operation of the pwm channel. any value written to the counter causes the counter to reset to $00, the counter direction to be set to up, the immediate load of both duty and period registers with values from the buffers, and the output to change according to the polarity bit. when the channel is disabled (pwmex = 0), the counter stops. when a channel becomes enabled (pwmex = 1), the associated pwm counter continues from the count in the pwmcntx register. this allows the waveform to continue where it left off when the channel is re-enabled. when the channel is disabled, writing ? to the period register will cause the counter to reset on the next selected clock. note if the user wants to start a new ?lean?pwm waveform without any ?istory?from the old waveform, the user must write to channel counter (pwmcntx) prior to enabling the pwm channel (pwmex = 1). generally, writes to the counter are done prior to enabling a channel in order to start from a known state. however, writing a counter can also be done while the pwm channel is enabled (counting). the effect is similar to writing the counter when the channel is disabled, except that the new period is started immediately with the output set according to the polarity bit. note writing to the counter while the channel is enabled can cause an irregular pwm cycle to occur. the counter is cleared at the end of the effective period (see section 12.4.2.5, ?eft aligned outputs and section 12.4.2.6, ?enter aligned outputs for more details). 12.4.2.5 left aligned outputs the pwm timer provides the choice of two types of outputs, left aligned or center aligned. they are selected with the caex bits in the pwmcae register. if the caex bit is cleared (caex = 0), the corresponding pwm output will be left aligned. in left aligned output mode, the 8-bit counter is con?ured as an up counter only. it compares to two registers, a duty register and a period register as shown in the block diagram in figure 12-19 . when the pwm counter matches the duty register the output ?p-?p changes state causing the pwm waveform to also change state. a match between the pwm counter and the period register resets the counter and the output ?p-?p, as shown in figure 12-19 , as well as performing a load from the double buffer period and duty register to the associated registers, as described in section 12.4.2.3, ?wm period and duty . the counter counts from 0 to the value in the period register ?1. table 12-10. pwm timer counter conditions counter clears ($00) counter counts counter stops when pwmcntx register written to any value when pwm channel is enabled (pwmex = 1). counts from last value in pwmcntx. when pwm channel is disabled (pwmex = 0) effective period ends chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 403 note changing the pwm output mode from left aligned to center aligned output (or vice versa) while channels are operating can cause irregularities in the pwm output. it is recommended to program the output mode before enabling the pwm channel. figure 12-20. pwm left aligned output waveform to calculate the output frequency in left aligned output mode for a particular channel, take the selected clock source frequency for the channel (a, b, sa, or sb) and divide it by the value in the period register for that channel. pwmx frequency = clock (a, b, sa, or sb) / pwmperx pwmx duty cycle (high time as a% of period): polarity = 0 (ppolx = 0) duty cycle = [(pwmperx-pwmdtyx)/pwmperx] * 100% polarity = 1 (ppolx = 1) duty cycle = [pwmdtyx / pwmperx] * 100% as an example of a left aligned output, consider the following case: clock source = e, where e = 10 mhz (100 ns period) ppolx = 0 pwmperx = 4 pwmdtyx = 1 pwmx frequency = 10 mhz/4 = 2.5 mhz pwmx period = 400 ns pwmx duty cycle = 3/4 *100% = 75% the output waveform generated is shown in figure 12-21 . pwmdtyx period = pwmperx ppolx = 0 ppolx = 1 chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 404 freescale semiconductor figure 12-21. pwm left aligned output example waveform 12.4.2.6 center aligned outputs for center aligned output mode selection, set the caex bit (caex = 1) in the pwmcae register and the corresponding pwm output will be center aligned. the 8-bit counter operates as an up/down counter in this mode and is set to up whenever the counter is equal to $00. the counter compares to two registers, a duty register and a period register as shown in the block diagram in figure 12-19 . when the pwm counter matches the duty register, the output ?p-?p changes state, causing the pwm waveform to also change state. a match between the pwm counter and the period register changes the counter direction from an up-count to a down-count. when the pwm counter decrements and matches the duty register again, the output ?p-?p changes state causing the pwm output to also change state. when the pwm counter decrements and reaches zero, the counter direction changes from a down-count back to an up-count and a load from the double buffer period and duty registers to the associated registers is performed, as described in section 12.4.2.3, ?wm period and duty . the counter counts from 0 up to the value in the period register and then back down to 0. thus the effective period is pwmperx*2. note changing the pwm output mode from left aligned to center aligned output (or vice versa) while channels are operating can cause irregularities in the pwm output. it is recommended to program the output mode before enabling the pwm channel. figure 12-22. pwm center aligned output waveform period = 400 ns e = 100 ns duty cycle = 75% ppolx = 0 ppolx = 1 pwmdtyx pwmdtyx period = pwmperx*2 pwmperx pwmperx chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 405 to calculate the output frequency in center aligned output mode for a particular channel, take the selected clock source frequency for the channel (a, b, sa, or sb) and divide it by twice the value in the period register for that channel. pwmx frequency = clock (a, b, sa, or sb) / (2*pwmperx) pwmx duty cycle (high time as a% of period): polarity = 0 (ppolx = 0) duty cycle = [(pwmperx-pwmdtyx)/pwmperx] * 100% polarity = 1 (ppolx = 1) duty cycle = [pwmdtyx / pwmperx] * 100% chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 406 freescale semiconductor as an example of a center aligned output, consider the following case: clock source = e, where e = 10 mhz (100 ns period) ppolx = 0 pwmperx = 4 pwmdtyx = 1 pwmx frequency = 10 mhz/8 = 1.25 mhz pwmx period = 800 ns pwmx duty cycle = 3/4 *100% = 75% shown in figure 12-23 is the output waveform generated. figure 12-23. pwm center aligned output example waveform 12.4.2.7 pwm 16-bit functions the pwm timer also has the option of generating 8-channels of 8-bits or 4-channels of 16-bits for greater pwm resolution. this 16-bit channel option is achieved through the concatenation of two 8-bit channels. the pwmctl register contains four control bits, each of which is used to concatenate a pair of pwm channels into one 16-bit channel. channels 6 and 7 are concatenated with the con67 bit, channels 4 and 5 are concatenated with the con45 bit, channels 2 and 3 are concatenated with the con23 bit, and channels 0 and 1 are concatenated with the con01 bit. note change these bits only when both corresponding channels are disabled. when channels 6 and 7 are concatenated, channel 6 registers become the high order bytes of the double byte channel, as shown in figure 12-24 . similarly, when channels 4 and 5 are concatenated, channel 4 registers become the high order bytes of the double byte channel. when channels 2 and 3 are concatenated, channel 2 registers become the high order bytes of the double byte channel. when channels 0 and 1 are concatenated, channel 0 registers become the high order bytes of the double byte channel. when using the 16-bit concatenated mode, the clock source is determined by the low order 8-bit channel clock select control bits. that is channel 7 when channels 6 and 7 are concatenated, channel 5 when channels 4 and 5 are concatenated, channel 3 when channels 2 and 3 are concatenated, and channel 1 when channels 0 and 1 are concatenated. the resulting pwm is output to the pins of the corresponding low order 8-bit channel as also shown in figure 12-24 . the polarity of the resulting pwm output is controlled by the ppolx bit of the corresponding low order 8-bit channel as well. e = 100 ns duty cycle = 75% e = 100 ns period = 800 ns chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 407 figure 12-24. pwm 16-bit mode once concatenated mode is enabled (conxx bits set in pwmctl register), enabling/disabling the corresponding 16-bit pwm channel is controlled by the low order pwmex bit. in this case, the high order bytes pwmex bits have no effect and their corresponding pwm output is disabled. in concatenated mode, writes to the 16-bit counter by using a 16-bit access or writes to either the low or high order byte of the counter will reset the 16-bit counter. reads of the 16-bit counter must be made by 16-bit access to maintain data coherency. pwmcnt6 pwcnt7 pwm7 clock source 7 high low period/duty compare pwmcnt4 pwcnt5 pwm5 clock source 5 high low period/duty compare pwmcnt2 pwcnt3 pwm3 clock source 3 high low period/duty compare pwmcnt0 pwcnt1 pwm1 clock source 1 high low period/duty compare chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 408 freescale semiconductor either left aligned or center aligned output mode can be used in concatenated mode and is controlled by the low order caex bit. the high order caex bit has no effect. table 12-11 is used to summarize which channels are used to set the various control bits when in 16-bit mode. 12.4.2.8 pwm boundary cases table 12-12 summarizes the boundary conditions for the pwm regardless of the output mode (left aligned or center aligned) and 8-bit (normal) or 16-bit (concatenation). 12.5 resets the reset state of each individual bit is listed within the section 12.3.2, ?egister descriptions which details the registers and their bit-?lds. all special functions or modes which are initialized during or just following reset are described within this section. the 8-bit up/down counter is con?ured as an up counter out of reset. all the channels are disabled and all the counters do not count. table 12-11. 16-bit concatenation mode summary conxx pwmex ppolx pclkx caex pwmx output con67 pwme7 ppol7 pclk7 cae7 pwm7 con45 pwme5 ppol5 pclk5 cae5 pwm5 con23 pwme3 ppol3 pclk3 cae3 pwm3 con01 pwme1 ppol1 pclk1 cae1 pwm1 table 12-12. pwm boundary cases pwmdtyx pwmperx ppolx pwmx output $00 (indicates no duty) >$00 1 always low $00 (indicates no duty) >$00 0 always high xx $00 1 (indicates no period) 1 counter = $00 and does not count. 1 always high xx $00 1 (indicates no period) 0 always low >= pwmperx xx 1 always high >= pwmperx xx 0 always low chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 409 12.6 interrupts the pwm module has only one interrupt which is generated at the time of emergency shutdown, if the corresponding enable bit (pwmie) is set. this bit is the enable for the interrupt. the interrupt ?g pwmif is set whenever the input level of the pwm7 channel changes while pwm7ena = 1 or when pwmena is being asserted while the level at pwm7 is active. in stop mode or wait mode (with the pswai bit set), the emergency shutdown feature will drive the pwm outputs to their shutdown output levels but the pwmif ?g will not be set. a description of the registers involved and affected due to this interrupt is explained in section 12.3.2.15, ?wm shutdown register (pwmsdn) . the pwm block only generates the interrupt and does not service it. the interrupt signal name is pwm interrupt signal. chapter 12 pulse-width modulator (pwm8b8cv1) mc9s12kg128 data sheet, rev. 1.15 410 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 411 chapter 13 timer module (tim16b8cv1) 13.1 introduction the basic timer consists of a 16-bit, software-programmable counter driven by a seven-stage programmable prescaler. this timer can be used for many purposes, including input waveform measurements while simultaneously generating an output waveform. pulse widths can vary from microseconds to many seconds. this timer contains 8 complete input capture/output compare channels and one pulse accumulator. the input capture function is used to detect a selected transition edge and record the time. the output compare function is used for generating output signals or for timer software delays. the 16-bit pulse accumulator is used to operate as a simple event counter or a gated time accumulator. the pulse accumulator shares timer channel 7 when in event mode. a full access for the counter registers or the input capture/output compare registers should take place in one clock cycle. accessing high byte and low byte separately for all of these registers may not yield the same result as accessing them in one word. 13.1.1 features the tim16b8c includes these distinctive features: eight input capture/output compare channels. clock prescaling. 16-bit counter. 16-bit pulse accumulator. 13.1.2 modes of operation stop: timer is off because clocks are stopped. freeze: timer counter keep on running, unless tsfrz in tscr (0x0006) is set to 1. wait: counters keep on running, unless tswai in tscr (0x0006) is set to 1. normal: timer counter keep on running, unless ten in tscr (0x0006) is cleared to 0. chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 412 freescale semiconductor 13.1.3 block diagrams figure 13-1. tim16b8c block diagram prescaler 16-bit counter input capture output compare 16-bit pulse accumulator ioc0 ioc2 ioc1 ioc5 ioc3 ioc4 ioc6 ioc7 pa input interrupt pa overflow interrupt timer overflow interrupt timer channel 0 interrupt timer channel 7 interrupt registers bus clock input capture output compare input capture output compare input capture output compare input capture output compare input capture output compare input capture output compare input capture output compare channel 0 channel 1 channel 2 channel 3 channel 4 channel 5 channel 6 channel 7 chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 413 figure 13-2. 16-bit pulse accumulator block diagram figure 13-3. interrupt flag setting edge detector intermodule bus pt7 m clock divide by 64 clock select clk0 clk1 4:1 mux timclk paclk paclk / 256 paclk / 65536 prescaled clock (pclk) (timer clock) interrupt mux (pamod) pacnt ptn edge detector 16-bit main timer tcn input capture reg. set cnf interrupt chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 414 freescale semiconductor figure 13-4. channel 7 output compare/pulse accumulator logic note for more information see the respective functional descriptions in section 13.4, ?unctional description , of this document. 13.2 external signal description the tim16b8c module has a total of eight external pins. 13.2.1 ioc7 ?input capture and output compare channel 7 pin this pin serves as input capture or output compare for channel 7. this can also be con?ured as pulse accumulator input. 13.2.2 ioc6 ?input capture and output compare channel 6 pin this pin serves as input capture or output compare for channel 6. 13.2.3 ioc5 ?input capture and output compare channel 5 pin this pin serves as input capture or output compare for channel 5. 13.2.4 ioc4 ?input capture and output compare channel 4 pin this pin serves as input capture or output compare for channel 4. pin 13.2.5 ioc3 ?input capture and output compare channel 3 pin this pin serves as input capture or output compare for channel 3. pulse accumulator pa d om7 ol7 oc7m7 channel 7 output compare chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 415 13.2.6 ioc2 ?input capture and output compare channel 2 pin this pin serves as input capture or output compare for channel 2. 13.2.7 ioc1 ?input capture and output compare channel 1 pin this pin serves as input capture or output compare for channel 1. 13.2.8 ioc0 ?input capture and output compare channel 0 pin this pin serves as input capture or output compare for channel 0. note for the description of interrupts see section 13.6, ?nterrupts . 13.3 memory map and register de?ition this section provides a detailed description of all memory and registers. 13.3.1 module memory map the memory map for the tim16b8c module is given below in table 13-1 . the address listed for each register is the address offset. the total address for each register is the sum of the base address for the tim16b8c module and the address offset for each register. chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 416 freescale semiconductor table 13-1. tim16b8c memory map address offset use access 0x0000 timer input capture/output compare select (tios) r/w 0x0001 timer compare force register (cforc) r/w 1 1 always read 0x0000. 0x0002 output compare 7 mask register (oc7m) r/w 0x0003 output compare 7 data register (oc7d) r/w 0x0004 timer count register (tcnt(hi)) r/w 2 2 only writable in special modes (test_mode = 1). 0x0005 timer count register (tcnt(lo)) r/w 2 0x0006 timer system control register1 (tscr1) r/w 0x0007 timer toggle over?w register (ttov) r/w 0x0008 timer control register1 (tctl1) r/w 0x0009 timer control register2 (tctl2) r/w 0x000a timer control register3 (tctl3) r/w 0x000b timer control register4 (tctl4) r/w 0x000c timer interrupt enable register (tie) r/w 0x000d timer system control register2 (tscr2) r/w 0x000e main timer interrupt flag1 (tflg1) r/w 0x000f main timer interrupt flag2 (tflg2) r/w 0x0010 timer input capture/output compare register 0 (tc0(hi)) r/w 3 3 write to these registers have no meaning or effect during input capture. 0x0011 timer input capture/output compare register 0 (tc0(lo)) r/w 3 0x0012 timer input capture/output compare register 1 (tc1(hi)) r/w 3 0x0013 timer input capture/output compare register 1 (tc1(lo)) r/w 3 0x0014 timer input capture/output compare register 2 (tc2(hi)) r/w 3 0x0015 timer input capture/output compare register 2 (tc2(lo)) r/w 3 0x0016 timer input capture/output compare register 3 (tc3(hi)) r/w 3 0x0017 timer input capture/output compare register 3 (tc3(lo)) r/w 3 0x0018 timer input capture/output compare register4 (tc4(hi)) r/w 3 0x0019 timer input capture/output compare register 4 (tc4(lo)) r/w 3 0x001a timer input capture/output compare register 5 (tc5(hi)) r/w 3 0x001b timer input capture/output compare register 5 (tc5(lo)) r/w 3 0x001c timer input capture/output compare register 6 (tc6(hi)) r/w 3 0x001d timer input capture/output compare register 6 (tc6(lo)) r/w 3 0x001e timer input capture/output compare register 7 (tc7(hi)) r/w 3 0x001f timer input capture/output compare register 7 (tc7(lo)) r/w 3 0x0020 16-bit pulse accumulator control register (pactl) r/w 0x0021 pulse accumulator flag register (paflg) r/w 0x0022 pulse accumulator count register (pacnt(hi)) r/w 0x0023 pulse accumulator count register (pacnt(lo)) r/w 0x0024 ?0x002c reserved 4 0x002d timer test register (timtst) r/w 2 0x002e ?0x002f reserved 4 chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 417 13.3.2 register descriptions this section consists of register descriptions in address order. each description includes a standard register diagram with an associated ?ure number. details of register bit and ?ld function follow the register diagrams, in bit order. 4 write has no effect; return 0 on read register name bit 7 654321 bit 0 0x0000 tios r ios7 ios6 ios5 ios4 ios3 ios2 ios1 ios0 w 0x0001 cforc r00000000 w foc7 foc6 foc5 foc4 foc3 foc2 foc1 foc0 0x0002 oc7m r oc7m7 oc7m6 oc7m5 oc7m4 oc7m3 oc7m2 oc7m1 oc7m0 w 0x0003 oc7d r oc7d7 oc7d6 oc7d5 oc7d4 oc7d3 oc7d2 oc7d1 oc7d0 w 0x0004 tcnth r tcnt15 tcnt14 tcnt13 tcnt12 tcnt11 tcnt10 tcnt9 tcnt8 w 0x0005 tcntl r tcnt7 tcnt6 tcnt5 tcnt4 tcnt3 tcnt2 tcnt1 tcnt0 w 0x0006 tscr2 r ten tswai tsfrz tffca 0000 w 0x0007 ttov r tov7 tov6 tov5 tov4 tov3 tov2 tov1 tov0 w 0x0008 tctl1 r om7 ol7 om6 ol6 om5 ol5 om4 ol4 w 0x0009 tctl2 r om3 ol3 om2 ol2 om1 ol1 om0 ol0 w 0x000a tctl3 r edg7b edg7a edg6b edg6a edg5b edg5a edg4b edg4a w 0x000b tctl4 r edg3b edg3a edg2b edg2a edg1b edg1a edg0b edg0a w = unimplemented or reserved figure 13-5. tim16b8c register summary chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 418 freescale semiconductor 13.3.2.1 timer input capture/output compare select (tios) 0x000c tie r c7i c6i c5i c4i c3i c2i c1i c0i w 0x000d tscr2 r toi 000 tcre pr2 pr1 pr0 w 0x000e tflg1 r c7f c6f c5f c4f c3f c2f c1f c0f w 0x000f tflg2 r tof 0000000 w 0x0010?x001f tcxh?cxl r bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 w r bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 w 0x0020 pactl r0 paen pamod pedge clk1 clk0 paovi pai w 0x0021 paflg r000000 paovf paif w 0x0022 pacnth r pacnt15 pacnt14 pacnt13 pacnt12 pacnt11 pacnt10 pacnt9 pacnt8 w 0x0023 pacntl r pacnt7 pacnt6 pacnt5 pacnt4 pacnt3 pacnt2 pacnt1 pacnt0 w 0x0024?x002f reserved r w 76543210 r ios7 ios6 ios5 ios4 ios3 ios2 ios1 ios0 w reset 0 0 0 00000 figure 13-6. timer input capture/output compare select (tios) register name bit 7 654321 bit 0 = unimplemented or reserved figure 13-5. tim16b8c register summary (continued) chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 419 read: anytime write: anytime 13.3.2.2 timer compare force register (cforc) read: anytime but will always return 0x0000 (1 state is transient) write: anytime 13.3.2.3 output compare 7 mask register (oc7m) read: anytime write: anytime table 13-2. tios field descriptions field description 7:0 ios[7:0] input capture or output compare channel con?uration 0 the corresponding channel acts as an input capture. 1 the corresponding channel acts as an output compare. 76543210 r00000000 w foc7 foc6 foc5 foc4 foc3 foc2 foc1 foc0 reset 0 0 0 00000 figure 13-7. timer compare force register (cforc) table 13-3. cforc field descriptions field description 7:0 foc[7:0] force output compare action for channel 7:0 a write to this register with the corresponding data bit(s) set causes the action which is programmed for output compare ??to occur immediately. the action taken is the same as if a successful comparison had just taken place with the tcx register except the interrupt ?g does not get set. note: a successful channel 7 output compare overrides any channel 6:0 compares. if forced output compare on any channel occurs at the same time as the successful output compare then forced output compare action will take precedence and interrupt ?g won? get set. 76543210 r oc7m7 oc7m6 oc7m5 oc7m4 oc7m3 oc7m2 oc7m1 oc7m0 w reset 0 0 0 00000 figure 13-8. output compare 7 mask register (oc7m) chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 420 freescale semiconductor 13.3.2.4 output compare 7 data register (oc7d) read: anytime write: anytime 13.3.2.5 timer count register (tcnt) the 16-bit main timer is an up counter. a full access for the counter register should take place in one clock cycle. a separate read/write for high byte and low byte will give a different result than accessing them as a word. table 13-4. oc7m field descriptions field description 7:0 oc7m[7:0] output compare 7 mask setting the oc7mx (x ranges from 0 to 6) will set the corresponding port to be an output port when the corresponding tiosx (x ranges from 0 to 6) bit is set to be an output compare. note: a successful channel 7 output compare overrides any channel 6:0 compares. for each oc7m bit that is set, the output compare action re?cts the corresponding oc7d bit. 76543210 r oc7d7 oc7d6 oc7d5 oc7d4 oc7d3 oc7d2 oc7d1 oc7d0 w reset 0 0 0 00000 figure 13-9. output compare 7 data register (oc7d) table 13-5. oc7d field descriptions field description 7:0 oc7d[7:0] output compare 7 data ?a channel 7 output compare can cause bits in the output compare 7 data register to transfer to the timer port data register depending on the output compare 7 mask register. 15 14 13 12 11 10 9 9 r tcnt15 tcnt14 tcnt13 tcnt12 tcnt11 tcnt10 tcnt9 tcnt8 w reset 0 0 0 00000 figure 13-10. timer count register high (tcnth) 76543210 r tcnt7 tcnt6 tcnt5 tcnt4 tcnt3 tcnt2 tcnt1 tcnt0 w reset 0 0 0 00000 figure 13-11. timer count register low (tcntl) chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 421 read: anytime write: has no meaning or effect in the normal mode; only writable in special modes (test_mode = 1). the period of the ?st count after a write to the tcnt registers may be a different size because the write is not synchronized with the prescaler clock. 13.3.2.6 timer system control register 1 (tscr1) read: anytime write: anytime 76543210 r ten tswai tsfrz tffca 0000 w reset 0 0 0 00000 = unimplemented or reserved figure 13-12. timer system control register 1 (tscr2) table 13-6. tscr1 field descriptions field description 7 ten timer enable 0 disables the main timer, including the counter. can be used for reducing power consumption. 1 allows the timer to function normally. if for any reason the timer is not active, there is no 64 clock for the pulse accumulator because the 64 is generated by the timer prescaler. 6 tswai timer module stops while in wait 0 allows the timer module to continue running during wait. 1 disables the timer module when the mcu is in the wait mode. timer interrupts cannot be used to get the mcu out of wait. tswai also affects pulse accumulator. 5 tsfrz timer stops while in freeze mode 0 allows the timer counter to continue running while in freeze mode. 1 disables the timer counter whenever the mcu is in freeze mode. this is useful for emulation. tsfrz does not stop the pulse accumulator. 4 tffca timer fast flag clear all 0 allows the timer ?g clearing to function normally. 1 for tflg1(0x000e), a read from an input capture or a write to the output compare channel (0x0010?x001f) causes the corresponding channel ?g, cnf, to be cleared. for tflg2 (0x000f), any access to the tcnt register (0x0004, 0x0005) clears the tof ?g. any access to the pacnt registers (0x0022, 0x0023) clears the paovf and paif ?gs in the paflg register (0x0021). this has the advantage of eliminating software overhead in a separate clear sequence. extra care is required to avoid accidental ?g clearing due to unintended accesses. chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 422 freescale semiconductor 13.3.2.7 timer toggle on over?w register 1 (ttov) read: anytime write: anytime 13.3.2.8 timer control register 1/timer control register 2 (tctl1/tctl2) read: anytime write: anytime 76543210 r tov7 tov6 tov5 tov4 tov3 tov2 tov1 tov0 w reset 0 0 0 00000 figure 13-13. timer toggle on over?w register 1 (ttov) table 13-7. ttov field descriptions field description 7:0 tov[7:0] toggle on over?w bits tovx toggles output compare pin on over?w. this feature only takes effect when in output compare mode. when set, it takes precedence over forced output compare but not channel 7 override events. 0 toggle output compare pin on over?w feature disabled. 1 toggle output compare pin on over?w feature enabled. 76543210 r om7 ol7 om6 ol6 om5 ol5 om4 ol4 w reset 0 0 0 00000 figure 13-14. timer control register 1 (tctl1) 76543210 r om3 ol3 om2 ol2 om1 ol1 om0 ol0 w reset 0 0 0 00000 figure 13-15. timer control register 2 (tctl2) chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 423 to operate the 16-bit pulse accumulator independently of input capture or output compare 7 and 0 respectively the user must set the corresponding bits iosx = 1, omx = 0 and olx = 0. oc7m7 in the oc7m register must also be cleared. table 13-8. tctl1/tctl2 field descriptions field description 7:0 omx output mode these eight pairs of control bits are encoded to specify the output action to be taken as a result of a successful ocx compare. when either omx or olx is 1, the pin associated with ocx becomes an output tied to ocx. note: to enable output action by omx bits on timer port, the corresponding bit in oc7m should be cleared. 7:0 olx output level these eight pairs of control bits are encoded to specify the output action to be taken as a result of a successful ocx compare. when either omx or olx is 1, the pin associated with ocx becomes an output tied to ocx. note: to enable output action by olx bits on timer port, the corresponding bit in oc7m should be cleared. table 13-9. compare result output action omx olx action 0 0 timer disconnected from output pin logic 0 1 toggle ocx output line 1 0 clear ocx output line to zero 1 1 set ocx output line to one chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 424 freescale semiconductor 13.3.2.9 timer control register 3/timer control register 4 (tctl3 and tctl4) read: anytime write: anytime. 76543210 r edg7b edg7a edg6b edg6a edg5b edg5a edg4b edg4a w reset 0 0 0 00000 figure 13-16. timer control register 3 (tctl3) 76543210 r edg3b edg3a edg2b edg2a edg1b edg1a edg0b edg0a w reset 0 0 0 00000 figure 13-17. timer control register 4 (tctl4) table 13-10. tctl3/tctl4 field descriptions field description 7:0 edgnb edgna input capture edge control ?these eight pairs of control bits con?ure the input capture edge detector circuits. table 13-11. edge detector circuit con?uration edgnb edgna con?uration 0 0 capture disabled 0 1 capture on rising edges only 1 0 capture on falling edges only 1 1 capture on any edge (rising or falling) chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 425 13.3.2.10 timer interrupt enable register (tie) read: anytime write: anytime. 13.3.2.11 timer system control register 2 (tscr2) read: anytime write: anytime. 76543210 r c7i c6i c5i c4i c3i c2i c1i c0i w reset 0 0 0 00000 figure 13-18. timer interrupt enable register (tie) table 13-12. tie field descriptions field description 7:0 c7i:c0i input capture/output compare ??interrupt enable the bits in tie correspond bit-for-bit with the bits in the tflg1 status register. if cleared, the corresponding ?g is disabled from causing a hardware interrupt. if set, the corresponding ?g is enabled to cause a interrupt. 76543210 r toi 000 tcre pr2 pr1 pr0 w reset 0 0 0 00000 = unimplemented or reserved figure 13-19. timer system control register 2 (tscr2) table 13-13. tscr2 field descriptions field description 7 toi timer over?w interrupt enable 0 interrupt inhibited. 1 hardware interrupt requested when tof ?g set. 3 tcre timer counter reset enable this bit allows the timer counter to be reset by a successful output compare 7 event. this mode of operation is similar to an up-counting modulus counter. 0 counter reset inhibited and counter free runs. 1 counter reset by a successful output compare 7. if tc7 = 0x0000 and tcre = 1, tcnt will stay at 0x0000 continuously. if tc7 = 0xffff and tcre = 1, tof will never be set when tcnt is reset from 0xffff to 0x0000. 2 pr[2:0] timer prescaler select ?these three bits select the frequency of the timer prescaler clock derived from the bus clock as shown in table 13-14 . chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 426 freescale semiconductor note the newly selected prescale factor will not take effect until the next synchronized edge where all prescale counter stages equal zero. 13.3.2.12 main timer interrupt flag 1 (tflg1) read: anytime write: used in the clearing mechanism (set bits cause corresponding bits to be cleared). writing a zero will not affect current status of the bit. table 13-14. timer clock selection pr2 pr1 pr0 timer clock 0 0 0 bus clock / 1 0 0 1 bus clock / 2 0 1 0 bus clock / 4 0 1 1 bus clock / 8 1 0 0 bus clock / 16 1 0 1 bus clock / 32 1 1 0 bus clock / 64 1 1 1 bus clock / 128 76543210 r c7f c6f c5f c4f c3f c2f c1f c0f w reset 0 0 0 00000 figure 13-20. main timer interrupt flag 1 (tflg1) table 13-15. trlg1 field descriptions field description 7:0 c[7:0]f input capture/output compare channel ??flag ?these flags are set when an input capture or output compare event occurs. clear a channel ?g by writing one to it. when tffca bit in tscr register is set, a read from an input capture or a write into an output compare channel (0x0010?x001f) will cause the corresponding channel ?g cxf to be cleared. chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 427 13.3.2.13 main timer interrupt flag 2 (tflg2) tflg2 indicates when interrupt conditions have occurred. to clear a bit in the ?g register, write the bit to one. read: anytime write: used in clearing mechanism (set bits cause corresponding bits to be cleared). any access to tcnt will clear tflg2 register if the tffca bit in tscr register is set. 13.3.2.14 timer input capture/output compare registers high and low 0? (tcxh and tcxl) depending on the tios bit for the corresponding channel, these registers are used to latch the value of the free-running counter when a de?ed transition is sensed by the corresponding input capture edge detector or to trigger an output action for output compare. read: anytime 76543210 r tof 0000000 w reset 0 0 0 00000 unimplemented or reserved figure 13-21. main timer interrupt flag 2 (tflg2) table 13-16. trlg2 field descriptions field description 7 tof timer over?w flag set when 16-bit free-running timer over?ws from 0xffff to 0x0000. this bit is cleared automatically by a write to the tflg2 register with bit 7 set. (see also tcre control bit explanation.) 15 14 13 12 11 10 9 0 r bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 w reset 00000000 figure 13-22. timer input capture/output compare register x high (tcxh) 76543210 r bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 w reset 00000000 figure 13-23. timer input capture/output compare register x low (tcxl) chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 428 freescale semiconductor write: anytime for output compare function.writes to these registers have no meaning or effect during input capture. all timer input capture/output compare registers are reset to 0x0000. note read/write access in byte mode for high byte should takes place before low byte otherwise it will give a different result. 13.3.2.15 16-bit pulse accumulator control register (pactl) when paen is set, the pact is enabled.the pact shares the input pin with ioc7. read: any time write: any time 76543210 r0 paen pamod pedge clk1 clk0 paovi pai w reset 0 0 0 00000 unimplemented or reserved figure 13-24. 16-bit pulse accumulator control register (pactl) table 13-17. pactl field descriptions field description 6 paen pulse accumulator system enable ?paen is independent from ten. with timer disabled, the pulse accumulator can function unless pulse accumulator is disabled. 0 16-bit pulse accumulator system disabled. 1 pulse accumulator system enabled. 5 pamod pulse accumulator mode ?this bit is active only when the pulse accumulator is enabled (paen = 1). see table 13-18 . 0 event counter mode. 1 gated time accumulation mode. 4 pedge pulse accumulator edge control this bit is active only when the pulse accumulator is enabled (paen = 1). for pamod bit = 0 (event counter mode). see table 13-18 . 0 falling edges on ioc7 pin cause the count to be incremented. 1 rising edges on ioc7 pin cause the count to be incremented. for pamod bit = 1 (gated time accumulation mode). 0 ioc7 input pin high enables m (bus clock) divided by 64 clock to pulse accumulator and the trailing falling edge on ioc7 sets the paif ?g. 1 ioc7 input pin low enables m (bus clock) divided by 64 clock to pulse accumulator and the trailing rising edge on ioc7 sets the paif ?g. 3:2 clk[1:0] clock select bits refer to table 13-19 . chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 429 note if the timer is not active (ten = 0 in tscr), there is no divide-by-64 because the 64 clock is generated by the timer prescaler. for the description of paclk please refer figure 13-24 . if the pulse accumulator is disabled (paen = 0), the prescaler clock from the timer is always used as an input clock to the timer counter. the change from one selected clock to the other happens immediately after these bits are written. 1 paov i pulse accumulator over?w interrupt enable 0 interrupt inhibited. 1 interrupt requested if paovf is set. 0 pa i pulse accumulator input interrupt enable 0 interrupt inhibited. 1 interrupt requested if paif is set. table 13-18. pin action pamod pedge pin action 0 0 falling edge 0 1 rising edge 1 0 div. by 64 clock enabled with pin high level 1 1 div. by 64 clock enabled with pin low level table 13-19. timer clock selection clk1 clk0 timer clock 0 0 use timer prescaler clock as timer counter clock 0 1 use paclk as input to timer counter clock 1 0 use paclk/256 as timer counter clock frequency 1 1 use paclk/65536 as timer counter clock frequency table 13-17. pactl field descriptions (continued) field description chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 430 freescale semiconductor 13.3.2.16 pulse accumulator flag register (paflg) read: anytime write: anytime when the tffca bit in the tscr register is set, any access to the pacnt register will clear all the ?gs in the paflg register. 76543210 r000000 paovf paif w reset 0 0 0 00000 unimplemented or reserved figure 13-25. pulse accumulator flag register (paflg) table 13-20. paflg field descriptions field description 1 paov f pulse accumulator over?w flag set when the 16-bit pulse accumulator over?ws from 0xffff to 0x0000. this bit is cleared automatically by a write to the paflg register with bit 1 set. 0 paif pulse accumulator input edge flag set when the selected edge is detected at the ioc7 input pin.in event mode the event edge triggers paif and in gated time accumulation mode the trailing edge of the gate signal at the ioc7 input pin triggers paif. this bit is cleared by a write to the paflg register with bit 0 set. any access to the pacnt register will clear all the ?gs in this register when tffca bit in register tscr(0x0006) is set. chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 431 13.3.2.17 pulse accumulators count registers (pacnt) read: anytime write: anytime these registers contain the number of active input edges on its input pin since the last reset. when pacnt over?ws from 0xffff to 0x0000, the interrupt ?g paovf in paflg (0x0021) is set. full count register access should take place in one clock cycle. a separate read/write for high byte and low byte will give a different result than accessing them as a word. note reading the pulse accumulator counter registers immediately after an active edge on the pulse accumulator input pin may miss the last count because the input has to be synchronized with the bus clock ?st. 13.4 functional description this section provides a complete functional description of the timer tim16b8c block. please refer to the detailed timer block diagram in figure 13-28 as necessary. 15 14 13 12 11 10 9 0 r pacnt15 pacnt14 pacnt13 pacnt12 pacnt11 pacnt10 pacnt9 pacnt8 w reset 0 0 0 00000 figure 13-26. pulse accumulator count register high (pacnth) 76543210 r pacnt7 pacnt6 pacnt5 pacnt4 pacnt3 pacnt2 pacnt1 pacnt0 w reset 0 0 0 00000 figure 13-27. pulse accumulator count register low (pacntl) chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 432 freescale semiconductor figure 13-28. detailed timer block diagram 13.4.1 prescaler the prescaler divides the bus clock by 1,2,4,8,16,32,64 or 128. the prescaler select bits, pr[2:0], select the prescaler divisor. pr[2:0] are in timer system control register 2 (tscr2). prescaler channel 0 ioc0 pin 16-bit counter logic pr[2:1:0] divide-by-64 tc0 edge detect pacnt(hi):pacnt(lo) paovf pedge paovi pamod pae 16-bit comparator tcnt(hi):tcnt(lo) channel 1 tc1 16-bit comparator 16-bit counter interrupt logic tof toi c0f c1f edge detect ioc1 pin logic edge detect cxf channel7 tc7 16-bit comparator c7f ioc7 pin logic edge detect om:ol0 tov0 om:ol1 tov1 om:o73 tov7 edg1a edg1b edg7a edg7b edg0b tcre paif clear counter paif pai interrupt logic cxi interrupt request paovf ch. 7 compare ch.7 capture ch. 1 capture mux clk[1:0] paclk paclk/256 paclk/65536 ioc1 pin ioc0 pin ioc7 pin paclk paclk/256 paclk/65536 te ch. 1 compare ch. 0compare ch. 0 capture pa input channel2 edg0a channel 7 output compare ioc0 ioc1 ioc7 bus clock bus clock paovf paovi tof c0f c1f c7f chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 433 13.4.2 input capture clearing the i/o (input/output) select bit, iosx, con?ures channel x as an input capture channel. the input capture function captures the time at which an external event occurs. when an active edge occurs on the pin of an input capture channel, the timer transfers the value in the timer counter into the timer channel registers, tcx. the minimum pulse width for the input capture input is greater than two bus clocks. an input capture on channel x sets the cxf ?g. the cxi bit enables the cxf ?g to generate interrupt requests. 13.4.3 output compare setting the i/o select bit, iosx, con?ures channel x as an output compare channel. the output compare function can generate a periodic pulse with a programmable polarity, duration, and frequency. when the timer counter reaches the value in the channel registers of an output compare channel, the timer can set, clear, or toggle the channel pin. an output compare on channel x sets the cxf ?g. the cxi bit enables the cxf ?g to generate interrupt requests. the output mode and level bits, omx and olx, select set, clear, toggle on output compare. clearing both omx and olx disconnects the pin from the output logic. setting a force output compare bit, focx, causes an output compare on channel x. a forced output compare does not set the channel ?g. a successful output compare on channel 7 overrides output compares on all other output compare channels. the output compare 7 mask register masks the bits in the output compare 7 data register. the timer counter reset enable bit, tcre, enables channel 7 output compares to reset the timer counter. a channel 7 output compare can reset the timer counter even if the ioc7 pin is being used as the pulse accumulator input. writing to the timer port bit of an output compare pin does not affect the pin state. the value written is stored in an internal latch. when the pin becomes available for general-purpose output, the last value written to the bit appears at the pin. 13.4.4 pulse accumulator the pulse accumulator (pacnt) is a 16-bit counter that can operate in two modes: event counter mode ?counting edges of selected polarity on the pulse accumulator input pin, pai. gated time accumulation mode counting pulses from a divide-by-64 clock. the pamod bit selects the mode of operation. the minimum pulse width for the pai input is greater than two bus clocks. chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 434 freescale semiconductor 13.4.5 event counter mode clearing the pamod bit con?ures the pacnt for event counter operation. an active edge on the ioc7 pin increments the pulse accumulator counter. the pedge bit selects falling edges or rising edges to increment the count. note the pacnt input and timer channel 7 use the same pin ioc7. to use the ioc7, disconnect it from the output logic by clearing the channel 7 output mode and output level bits, om7 and ol7. also clear the channel 7 output compare 7 mask bit, oc7m7. the pulse accumulator counter register re?ct the number of active input edges on the pacnt input pin since the last reset. the paovf bit is set when the accumulator rolls over from 0xffff to 0x0000. the pulse accumulator over?w interrupt enable bit, paovi, enables the paovf ?g to generate interrupt requests. note the pulse accumulator counter can operate in event counter mode even when the timer enable bit, ten, is clear. 13.4.6 gated time accumulation mode setting the pamod bit con?ures the pulse accumulator for gated time accumulation operation. an active level on the pacnt input pin enables a divided-by-64 clock to drive the pulse accumulator. the pedge bit selects low levels or high levels to enable the divided-by-64 clock. the trailing edge of the active level at the ioc7 pin sets the paif. the pai bit enables the paif ?g to generate interrupt requests. the pulse accumulator counter register re?ct the number of pulses from the divided-by-64 clock since the last reset. note the timer prescaler generates the divided-by-64 clock. if the timer is not active, there is no divided-by-64 clock. 13.5 resets the reset state of each individual bit is listed within section 13.3, ?emory map and register de?ition which details the registers and their bit ?lds. 13.6 interrupts this section describes interrupts originated by the tim16b8c block. table 13-21 lists the interrupts generated by the tim16b8c to communicate with the mcu. chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 435 the tim16b8c uses a total of 11 interrupt vectors. the interrupt vector offsets and interrupt numbers are chip dependent. 13.6.1 channel [7:0] interrupt (c[7:0]f) this active high outputs will be asserted by the module to request a timer channel 7 ?0 interrupt to be serviced by the system controller. 13.6.2 pulse accumulator input interrupt (paovi) this active high output will be asserted by the module to request a timer pulse accumulator input interrupt to be serviced by the system controller. 13.6.3 pulse accumulator over?w interrupt (paovf) this active high output will be asserted by the module to request a timer pulse accumulator over?w interrupt to be serviced by the system controller. 13.6.4 timer over?w interrupt (tof) this active high output will be asserted by the module to request a timer over?w interrupt to be serviced by the system controller. table 13-21. tim16b8cv1 interrupts interrupt offset 1 1 chip dependent. vector 1 priority 1 source description c[7:0]f timer channel 7? active high timer channel interrupts 7? paovi pulse accumulator input active high pulse accumulator input interrupt paovf pulse accumulator over?w pulse accumulator over?w interrupt tof timer over?w timer over?w interrupt chapter 13 timer module (tim16b8cv1) mc9s12kg128 data sheet, rev. 1.15 436 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 437 chapter 14 dual output voltage regulator (vreg3v3v2) 14.1 introduction the vreg3v3 is a dual output voltage regulator providing two separate 2.5 v (typical) supplies differing in the amount of current that can be sourced. the regulator input voltage range is from 3.3 v up to 5 v (typical). 14.1.1 features the block vreg3v3 includes these distinctive features: two parallel, linear voltage regulators bandgap reference low-voltage detect (lvd) with low-voltage interrupt (lvi) power-on reset (por) low-voltage reset (lvr) 14.1.2 modes of operation there are three modes vreg3v3 can operate in: full-performance mode (fpm) (mcu is not in stop mode) the regulator is active, providing the nominal supply voltage of 2.5 v with full current sourcing capability at both outputs. features lvd (low-voltage detect), lvr (low-voltage reset), and por (power-on reset) are available. reduced-power mode (rpm) (mcu is in stop mode) the purpose is to reduce power consumption of the device. the output voltage may degrade to a lower value than in full-performance mode, additionally the current sourcing capability is substantially reduced. only the por is available in this mode, lvd and lvr are disabled. shutdown mode controlled by v regen (see device overview chapter for connectivity of v regen ). this mode is characterized by minimum power consumption. the regulator outputs are in a high impedance state, only the por feature is available, lvd and lvr are disabled. this mode must be used to disable the chip internal regulator vreg3v3, i.e., to bypass the vreg3v3 to use external supplies. chapter 14 dual output voltage regulator (vreg3v3v2) mc9s12kg128 data sheet, rev. 1.15 438 freescale semiconductor 14.1.3 block diagram figure 14-1 shows the function principle of vreg3v3 by means of a block diagram. the regulator core reg consists of two parallel sub-blocks, reg1 and reg2, providing two independent output voltages. figure 14-1. vreg3v3 block diagram lv r lv d por v ddr v dd lvi por lvr ctrl v ss v ddpll v sspll v regen reg reg2 reg1 pin v dda v ssa reg: regulator core lvd: low voltage detect ctrl: regulator control lvr: low voltage reset por: power-on reset chapter 14 dual output voltage regulator (vreg3v3v2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 439 14.2 external signal description due to the nature of vreg3v3 being a voltage regulator providing the chip internal power supply voltages most signals are power supply signals connected to pads. table 14-1 shows all signals of vreg3v3 associated with pins. note check device overview chapter for connectivity of the signals. 14.2.1 v ddr ?regulator power input signal v ddr is the power input of vreg3v3. all currents sourced into the regulator loads flow through this pin. a chip external decoupling capacitor (100 nf...220 nf, x7r ceramic) between v ddr and v ssr can smoothen ripple on v ddr . for entering shutdown mode, pin v ddr should also be tied to ground on devices without a v regen pin. 14.2.2 v dda , v ssa ?regulator reference supply signals v dda /v ssa which are supposed to be relatively quiet are used to supply the analog parts of the regulator. internal precision reference circuits are supplied from these signals. a chip external decoupling capacitor (100 nf...220 nf, x7r ceramic) between v dda and v ssa can further improve the quality of this supply. table 14-1. vreg3v3 ?signal properties name port function reset state pull up v ddr vreg3v3 power input (positive supply) v dda vreg3v3 quiet input (positive supply) v ssa vreg3v3 quiet input (ground) v dd vreg3v3 primary output (positive supply) v ss vreg3v3 primary output (ground) v ddpll vreg3v3 secondary output (positive supply) v sspll vreg3v3 secondary output (ground) v regen (optional) vreg3v3 (optional) regulator enable chapter 14 dual output voltage regulator (vreg3v3v2) mc9s12kg128 data sheet, rev. 1.15 440 freescale semiconductor 14.2.3 v dd , v ss ?regulator output1 (core logic) signals v dd /v ss are the primary outputs of vreg3v3 that provide the power supply for the core logic. these signals are connected to device pins to allow external decoupling capacitors (100 nf...220 nf, x7r ceramic). in shutdown mode an external supply at v dd /v ss can replace the voltage regulator. 14.2.4 v ddpll , v sspll ?regulator output2 (pll) signals v ddpll /v sspll are the secondary outputs of vreg3v3 that provide the power supply for the pll and oscillator. these signals are connected to device pins to allow external decoupling capacitors (100 nf...220 nf, x7r ceramic). in shutdown mode an external supply at v ddpll /v sspll can replace the voltage regulator. 14.2.5 v regen ?optional regulator enable this optional signal is used to shutdown vreg3v3. in that case v dd /v ss and v ddpll /v sspll must be provided externally. shutdown mode is entered with v regen being low. if v regen is high, the vreg3v3 is either in full performance mode or in reduced power mode. for the connectivity of v regen see device overview chapter. note switching from fpm or rpm to shutdown of vreg3v3 and vice versa is not supported while the mcu is powered. 14.3 memory map and register de?ition this subsection provides a detailed description of all registers accessible in vreg3v3. 14.3.1 module memory map figure 14-2 provides an overview of all used registers. table 14-2. vreg3v3 memory map address offset use access 0x0000 vreg3v3 control register (vregctrl) r/w chapter 14 dual output voltage regulator (vreg3v3v2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 441 14.3.2 register descriptions the following paragraphs describe, in address order, all the vreg3v3 registers and their individual bits. 14.3.2.1 vreg3v3 ?control register (vregctrl) the vregctrl register allows to separately enable features of vreg3v3. note on entering the reduced power mode the lvif is not cleared by the vreg3v3. 14.4 functional description block vreg3v3 is a voltage regulator as depicted in figure 14-1 . the regulator functional elements are the regulator core (reg), a low-voltage detect module (lvd), a power-on reset module (por) and a low-voltage reset module (lvr). there is also the regulator control block (ctrl) which represents the interface to the digital core logic but also manages the operating modes of vreg3v3. 14.4.1 reg ?regulator core vreg3v3, respectively its regulator core has two parallel, independent regulation loops (reg1 and reg2) that differ only in the amount of current that can be sourced to the connected loads. therefore, only reg1 providing the supply at v dd /v ss is explained. the principle is also valid for reg2. 76543210 r00000lvds lvie lvif w reset 0 0 0 00000 = unimplemented or reserved figure 14-2. vreg3v3 ?control register (vregctrl) table 14-3. mcctl1 field descriptions field description 2 lvds low-voltage detect status bit ?this read-only status bit re?cts the input voltage. writes have no effect. 0 input voltage v dda is above level v lvid or rpm or shutdown mode. 1 input voltage v dda is below level v lvia and fpm. 1 lvie low-voltage interrupt enable bit 0 interrupt request is disabled. 1 interrupt will be requested whenever lvif is set. 0 lvif low-voltage interrupt flag lvif is set to 1 when lvds status bit changes. this ?g can only be cleared by writing a 1. writing a 0 has no effect. if enabled (lvie = 1), lvif causes an interrupt request. 0 no change in lvds bit. 1 lvds bit has changed. chapter 14 dual output voltage regulator (vreg3v3v2) mc9s12kg128 data sheet, rev. 1.15 442 freescale semiconductor the regulator is a linear series regulator with a bandgap reference in its full performance mode and a voltage clamp in reduced power mode. all load currents flow from input v ddr to v ss or v sspll , the reference circuits are connected to v dda and v ssa . 14.4.2 full-performance mode in full performance mode, a fraction of the output voltage (v dd ) and the bandgap reference voltage are fed to an operational amplifier. the amplified input voltage difference controls the gate of an output driver which basically is a large nmos transistor connected to the output. 14.4.3 reduced-power mode in reduced power mode, the driver gate is connected to a buffered fraction of the input voltage (v ddr ). the operational amplifier and the bandgap are disabled to reduce power consumption. 14.4.4 lvd ?low-voltage detect sub-block lvd is responsible for generating the low-voltage interrupt (lvi). lvd monitors the input voltage (v dda ? ssa ) and continuously updates the status flag lvds. interrupt flag lvif is set whenever status flag lvds changes its value. the lvd is available in fpm and is inactive in reduced power mode and shutdown mode. 14.4.5 por ?power-on reset this functional block monitors output v dd . if v dd is below v pord , signal por is high, if it exceeds v pord , the signal goes low. the transition to low forces the cpu in the power-on sequence. due to its role during chip power-up this module must be active in all operating modes of vreg3v3. 14.4.6 lvr ?low-voltage reset block lvr monitors the primary output voltage v dd . if it drops below the assertion level (v lvra ) signal lvr asserts and when rising above the deassertion level (v lvrd ) signal lvr negates again. the lvr function is available only in full performance mode. 14.4.7 ctrl ?regulator control this part contains the register block of vreg3v3 and further digital functionality needed to control the operating modes. ctrl also represents the interface to the digital core logic. chapter 14 dual output voltage regulator (vreg3v3v2) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 443 14.5 resets this subsection describes how vreg3v3 controls the reset of the mcu.the reset values of registers and signals are provided in section 14.3, ?emory map and register definition . possible reset sources are listed in table 14-4 . 14.5.1 power-on reset during chip power-up the digital core may not work if its supply voltage v dd is below the por deassertion level (v pord ). therefore, signal por which forces the other blocks of the device into reset is kept high until v dd exceeds v pord . then por becomes low and the reset generator of the device continues the start-up sequence. the power-on reset is active in all operation modes of vreg3v3. 14.5.2 low-voltage reset for details on low-voltage reset see section 14.4.6, ?vr ?low-voltage reset . 14.6 interrupts this subsection describes all interrupts originated by vreg3v3. the interrupt vectors requested by vreg3v3 are listed in table 14-5 . vector addresses and interrupt priorities are defined at mcu level. 14.6.1 lvi ?low-voltage interrupt in fpm vreg3v3 monitors the input voltage v dda . whenever v dda drops below level v lvia the status bit lvds is set to 1. vice versa, lvds is reset to 0 when v dda rises above level v lvid . an interrupt, indicated by flag lvif = 1, is triggered by any change of the status bit lvds if interrupt enable bit lvie = 1. note on entering the reduced power mode, the lvif is not cleared by the vreg3v3. table 14-4. vreg3v3 ?reset sources reset source local enable power-on reset always active low-voltage reset available only in full performance mode table 14-5. vreg3v3 ?interrupt vectors interrupt source local enable low voltage interrupt (lvi) lvie = 1; available only in full performance mode chapter 14 dual output voltage regulator (vreg3v3v2) mc9s12kg128 data sheet, rev. 1.15 444 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 445 chapter 15 background debug module (bdmv4) 15.1 introduction this section describes the functionality of the background debug module (bdm) sub-block of the hcs12 core platform. a block diagram of the bdm is shown in figure 15-1 . figure 15-1. bdm block diagram the background debug module (bdm) sub-block is a single-wire, background debug system implemented in on-chip hardware for minimal cpu intervention. all interfacing with the bdm is done via the bkgd pin. bdmv4 has enhanced capability for maintaining synchronization between the target and host while allowing more ?xibility in clock rates. this includes a sync signal to show the clock rate and a handshake signal to indicate when an operation is complete. the system is backwards compatible with older external interfaces. 15.1.1 features single-wire communication with host development system bdmv4 (and bdm2): enhanced capability for allowing more ?xibility in clock rates bdmv4: sync command to determine communication rate bdmv4: go_until command bdmv4: hardware handshake protocol to increase the performance of the serial communication active out of reset in special single-chip mode enbdm sdv 16-bit shift register bkgd clocks data address host system bus interface and control logic instruction decode and execution standard bdm firmware lookup table clksw bdmact entag trace chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 446 freescale semiconductor nine hardware commands using free cycles, if available, for minimal cpu intervention hardware commands not requiring active bdm 15 ?mware commands execute from the standard bdm ?mware lookup table instruction tagging capability software control of bdm operation during wait mode software selectable clocks when secured, hardware commands are allowed to access the register space in special single-chip mode, if the flash and eeprom erase tests fail. 15.1.2 modes of operation bdm is available in all operating modes but must be enabled before ?mware commands are executed. some system peripherals may have a control bit which allows suspending the peripheral function during background debug mode. 15.1.2.1 regular run modes all of these operations refer to the part in run mode. the bdm does not provide controls to conserve power during run mode. normal operation general operation of the bdm is available and operates the same in all normal modes. special single-chip mode in special single-chip mode, background operation is enabled and active out of reset. this allows programming a system with blank memory. special peripheral mode bdm is enabled and active immediately out of reset. bdm can be disabled by clearing the bdmact bit in the bdm status (bdmsts) register. the bdm serial system should not be used in special peripheral mode. emulation modes general operation of the bdm is available and operates the same as in normal modes. 15.1.2.2 secure mode operation if the part is in secure mode, the operation of the bdm is reduced to a small subset of its regular run mode operation. secure operation prevents access to flash or eeprom other than allowing erasure. 15.2 external signal description a single-wire interface pin is used to communicate with the bdm system. two additional pins are used for instruction tagging. these pins are part of the multiplexed external bus interface (mebi) sub-block and all interfacing between the mebi and bdm is done within the core interface boundary. functional descriptions of the pins are provided below for completeness. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 447 bkgd ?background interface pin t a ghi ?high byte instruction tagging pin t a glo ?low byte instruction tagging pin bkgd and t a ghi share the same pin. t a glo and lstrb share the same pin. note generally these pins are shared as described, but it is best to check the device overview chapter to make certain. all mcus at the time of this writing have followed this pin sharing scheme. 15.2.1 bkgd ?background interface pin debugging control logic communicates with external devices serially via the single-wire background interface pin (bkgd). during reset, this pin is a mode select input which selects between normal and special modes of operation. after reset, this pin becomes the dedicated serial interface pin for the background debug mode. 15.2.2 t a ghi ?high byte instruction tagging pin this pin is used to tag the high byte of an instruction. when instruction tagging is on, a logic 0 at the falling edge of the external clock (eclk) tags the high half of the instruction word being read into the instruction queue. 15.2.3 t a glo ?low byte instruction tagging pin this pin is used to tag the low byte of an instruction. when instruction tagging is on and low strobe is enabled, a logic 0 at the falling edge of the external clock (eclk) tags the low half of the instruction word being read into the instruction queue. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 448 freescale semiconductor 15.3 memory map and register de?ition a summary of the registers associated with the bdm is shown in figure 15-2 . registers are accessed by host-driven communications to the bdm hardware using read_bd and write_bd commands. detailed descriptions of the registers and associated bits are given in the subsections that follow. 15.3.1 module memory map table 15-1. int memory map register address use access reserved bdm status register (bdmsts) r/w reserved bdm ccr holding register (bdmccr) r/w 7 bdm internal register position (bdminr) r 8 reserved chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 449 15.3.2 register descriptions register name bit 7 6 5 4321 bit 0 reserved r x x x x x x 0 0 w bdmsts r enbdm bdmact entag sdv trace clksw unsec 0 w reserved r x x x xxxxx w reserved r x x x xxxxx w reserved r x x x xxxxx w reserved r x x x xxxxx w bdmccr r ccr7 ccr6 ccr5 ccr4 ccr3 ccr2 ccr1 ccr0 w bdminr r 0 reg14 reg13 reg12 reg11 0 0 0 w reserved r 0 0 0 00000 w reserved r 0 0 0 00000 w reserved r x x x xxxxx w reserved r x x x xxxxx w = unimplemented, reserved = implemented (do not alter) x = indeterminate 0 = always read zero figure 15-2. bdm register summary chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 450 freescale semiconductor 15.3.2.1 bdm status register (bdmsts) read: all modes through bdm operation write: all modes but subject to the following: bdmact can only be set by bdm hardware upon entry into bdm. it can only be cleared by the standard bdm ?mware lookup table upon exit from bdm active mode. clksw can only be written via bdm hardware or standard bdm ?mware write commands. all other bits, while writable via bdm hardware or standard bdm ?mware write commands, should only be altered by the bdm hardware or standard ?mware lookup table as part of bdm command execution. enbdm should only be set via a bdm hardware command if the bdm ?mware commands are needed. (this does not apply in special single-chip mode). 76543210 r enbdm bdmact entag sdv trace clksw unsec 0 w reset: special single-chip mode: special peripheral mode: all other modes: 1 1 0 0 0 1 enbdm is read as "1" by a debugging environment in special single-chip mode when the device is not secured or secured but fully erased (flash and eeprom).this is because the enbdm bit is set by the standard firmware before a bdm command can be fully transmitted and executed. 1 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 2 unsec is read as "1" by a debugging environment in special single-chip mode when the device is secured and fully erased, else it is "0" and can only be read if not secure (see also bit description). 0 0 0 0 = unimplemented or reserved = implemented (do not alter) figure 15-3. bdm status register (bdmsts) note: table 15-2. bdmsts field descriptions field description 7 enbdm enable bdm ?this bit controls whether the bdm is enabled or disabled. when enabled, bdm can be made active to allow ?mware commands to be executed. when disabled, bdm cannot be made active but bdm hardware commands are allowed. 0 bdm disabled 1 bdm enabled note: enbdm is set by the ?mware immediately out of reset in special single-chip mode. in secure mode, this bit will not be set by the ?mware until after the eeprom and flash erase verify tests are complete. 6 bdmact bdm active status ?this bit becomes set upon entering bdm. the standard bdm ?mware lookup table is then enabled and put into the memory map. bdmact is cleared by a carefully timed store instruction in the standard bdm ?mware as part of the exit sequence to return to user code and remove the bdm memory from the map. 0 bdm not active 1 bdm active chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 451 5 entag tagging enable ?this bit indicates whether instruction tagging in enabled or disabled. it is set when the taggo command is executed and cleared when bdm is entered. the serial system is disabled and the tag function enabled 16 cycles after this bit is written. bdm cannot process serial commands while tagging is active. 0 tagging not enabled or bdm active 1 tagging enabled 4 sdv shift data valid this bit is set and cleared by the bdm hardware. it is set after data has been transmitted as part of a ?mware read command or after data has been received as part of a ?mware write command. it is cleared when the next bdm command has been received or bdm is exited. sdv is used by the standard bdm ?mware to control program ?w execution. 0 data phase of command not complete 1 data phase of command is complete 3 trace trace1 bdm firmware command is being executed ?this bit gets set when a bdm trace1 ?mware command is ?st recognized. it will stay set as long as continuous back-to-back trace1 commands are executed. this bit will get cleared when the next command that is not a trace1 command is recognized. 0 trace1 command is not being executed 1 trace1 command is being executed 2 clksw clock switch the clksw bit controls which clock the bdm operates with. it is only writable from a hardware bdm command. a 150 cycle delay at the clock speed that is active during the data portion of the command will occur before the new clock source is guaranteed to be active. the start of the next bdm command uses the new clock for timing subsequent bdm communications. table 15-3 shows the resulting bdm clock source based on the clksw and the pllsel (pll select from the clock and reset generator) bits. note: the bdm alternate clock source can only be selected when clksw = 0 and pllsel = 1. the bdm serial interface is now fully synchronized to the alternate clock source, when enabled. this eliminates frequency restriction on the alternate clock which was required on previous versions. refer to the device overview section to determine which clock connects to the alternate clock source input. note: if the acknowledge function is turned on, changing the clksw bit will cause the ack to be at the new rate for the write command which changes it. 1 unsec unsecure this bit is only writable in special single-chip mode from the bdm secure ?mware and always gets reset to zero. it is in a zero state as secure mode is entered so that the secure bdm ?mware lookup table is enabled and put into the memory map along with the standard bdm ?mware lookup table. the secure bdm ?mware lookup table veri?s that the on-chip eeprom and flash eeprom are erased. this being the case, the unsec bit is set and the bdm program jumps to the start of the standard bdm ?mware lookup table and the secure bdm ?mware lookup table is turned off. if the erase test fails, the unsec bit will not be asserted. 0 system is in a secured mode 1 system is in a unsecured mode note: when unsec is set, security is off and the user can change the state of the secure bits in the on-chip flash eeprom. note that if the user does not change the state of the bits to ?nsecured?mode, the system will be secured again when it is next taken out of reset. table 15-3. bdm clock sources pllsel clksw bdmclk 0 0 bus clock 0 1 bus clock table 15-2. bdmsts field descriptions (continued) field description chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 452 freescale semiconductor 1 0 alternate clock (refer to the device overview chapter to determine the alternate clock source) 1 1 bus clock dependent on the pll table 15-3. bdm clock sources pllsel clksw bdmclk chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 453 15.3.2.2 bdm ccr holding register (bdmccr) read: all modes write: all modes note when bdm is made active, the cpu stores the value of the ccr register in the bdmccr register. however, out of special single-chip reset, the bdmccr is set to 0xd8 and not 0xd0 which is the reset value of the ccr register. when entering background debug mode, the bdm ccr holding register is used to save the contents of the condition code register of the user s program. it is also used for temporary storage in the standard bdm ?mware mode. the bdm ccr holding register can be written to modify the ccr value. 15.3.2.3 bdm internal register position register (bdminr) read: all modes write: never 76543210 r ccr7 ccr6 ccr5 ccr4 ccr3 ccr2 ccr1 ccr0 w reset 0 0 0 00000 figure 15-4. bdm ccr holding register (bdmccr) 76543210 r 0 reg14 reg13 reg12 reg11 0 0 0 w reset 0 0 0 00000 = unimplemented or reserved figure 15-5. bdm internal register position (bdminr) table 15-4. bdminr field descriptions field description 6:3 reg[14:11] internal register map position these four bits show the state of the upper ?e bits of the base address for the system s relocatable register block. bdminr is a shadow of the initrg register which maps the register block to any 2k byte space within the ?st 32k bytes of the 64k byte address space. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 454 freescale semiconductor 15.4 functional description the bdm receives and executes commands from a host via a single wire serial interface. there are two types of bdm commands, namely, hardware commands and ?mware commands. hardware commands are used to read and write target system memory locations and to enter active background debug mode, see section 15.4.3, ?dm hardware commands . target system memory includes all memory that is accessible by the cpu. firmware commands are used to read and write cpu resources and to exit from active background debug mode, see section 15.4.4, ?tandard bdm firmware commands . the cpu resources referred to are the accumulator (d), x index register (x), y index register (y), stack pointer (sp), and program counter (pc). hardware commands can be executed at any time and in any mode excluding a few exceptions as highlighted, see section 15.4.3, ?dm hardware commands . firmware commands can only be executed when the system is in active background debug mode (bdm). 15.4.1 security if the user resets into special single-chip mode with the system secured, a secured mode bdm ?mware lookup table is brought into the map overlapping a portion of the standard bdm ?mware lookup table. the secure bdm ?mware veri?s that the on-chip eeprom and flash eeprom are erased. this being the case, the unsec bit will get set. the bdm program jumps to the start of the standard bdm ?mware and the secured mode bdm ?mware is turned off and all bdm commands are allowed. if the eeprom or flash do not verify as erased, the bdm ?mware sets the enbdm bit, without asserting unsec, and the ?mware enters a loop. this causes the bdm hardware commands to become enabled, but does not enable the ?mware commands. this allows the bdm hardware to be used to erase the eeprom and flash. after execution of the secure ?mware, regardless of the results of the erase tests, the cpu registers, initee and ppage, will no longer be in their reset state. 15.4.2 enabling and activating bdm the system must be in active bdm to execute standard bdm ?mware commands. bdm can be activated only after being enabled. bdm is enabled by setting the enbdm bit in the bdm status (bdmsts) register. the enbdm bit is set by writing to the bdm status (bdmsts) register, via the single-wire interface, using a hardware command such as write_bd_byte. after being enabled, bdm is activated by one of the following 1 : hardware background command bdm external instruction tagging mechanism cpu bgnd instruction breakpoint sub-block s force or tag mechanism 2 when bdm is activated, the cpu ?ishes executing the current instruction and then begins executing the ?mware in the standard bdm ?mware lookup table. when bdm is activated by the breakpoint 1. bdm is enabled and active immediately out of special single-chip reset. 2. this method is only available on systems that have a a breakpoint or a debug sub-block. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 455 sub-block, the type of breakpoint used determines if bdm becomes active before or after execution of the next instruction. note if an attempt is made to activate bdm before being enabled, the cpu resumes normal instruction execution after a brief delay. if bdm is not enabled, any hardware background commands issued are ignored by the bdm and the cpu is not delayed. in active bdm, the bdm registers and standard bdm ?mware lookup table are mapped to addresses 0xff00 to 0xffff. bdm registers are mapped to addresses 0xff00 to 0xff07. the bdm uses these registers which are readable anytime by the bdm. however, these registers are not readable by user programs. 15.4.3 bdm hardware commands hardware commands are used to read and write target system memory locations and to enter active background debug mode. target system memory includes all memory that is accessible by the cpu such as on-chip ram, eeprom, flash eeprom, i/o and control registers, and all external memory. hardware commands are executed with minimal or no cpu intervention and do not require the system to be in active bdm for execution, although they can continue to be executed in this mode. when executing a hardware command, the bdm sub-block waits for a free cpu bus cycle so that the background access does not disturb the running application program. if a free cycle is not found within 128 clock cycles, the cpu is momentarily frozen so that the bdm can steal a cycle. when the bdm ?ds a free cycle, the operation does not intrude on normal cpu operation provided that it can be completed in a single cycle. however, if an operation requires multiple cycles the cpu is frozen until the operation is complete, even though the bdm found a free cycle. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 456 freescale semiconductor the bdm hardware commands are listed in table 15-5 . note: if enabled, ack will occur when data is ready for transmission for all bdm read commands and will occur after the write is complete for all bdm write commands. the read_bd and write_bd commands allow access to the bdm register locations. these locations are not normally in the system memory map but share addresses with the application in memory. to distinguish between physical memory locations that share the same address, bdm memory resources are enabled just for the read_bd and write_bd access cycle. this allows the bdm to access bdm locations unobtrusively, even if the addresses con?ct with the application memory map. 15.4.4 standard bdm firmware commands firmware commands are used to access and manipulate cpu resources. the system must be in active bdm to execute standard bdm ?mware commands, see section 15.4.2, ?nabling and activating bdm . normal instruction execution is suspended while the cpu executes the ?mware located in the standard bdm ?mware lookup table. the hardware command background is the usual way to activate bdm. as the system enters active bdm, the standard bdm ?mware lookup table and bdm registers become visible in the on-chip memory map at 0xff00?xffff, and the cpu begins executing the standard bdm table 15-5. hardware commands command opcode (hex) data description background 90 none enter background mode if ?mware is enabled. if enabled, an ack will be issued when the part enters active background mode. ack_enable d5 none enable handshake. issues an ack pulse after the command is executed. ack_disable d6 none disable handshake. this command does not issue an ack pulse. read_bd_byte e4 16-bit address 16-bit data out read from memory with standard bdm ?mware lookup table in map. odd address data on low byte; even address data on high byte. read_bd_word ec 16-bit address 16-bit data out read from memory with standard bdm ?mware lookup table in map. must be aligned access. read_byte e0 16-bit address 16-bit data out read from memory with standard bdm ?mware lookup table out of map. odd address data on low byte; even address data on high byte. read_word e8 16-bit address 16-bit data out read from memory with standard bdm ?mware lookup table out of map. must be aligned access. write_bd_byte c4 16-bit address 16-bit data in write to memory with standard bdm ?mware lookup table in map. odd address data on low byte; even address data on high byte. write_bd_word cc 16-bit address 16-bit data in write to memory with standard bdm ?mware lookup table in map. must be aligned access. write_byte c0 16-bit address 16-bit data in write to memory with standard bdm ?mware lookup table out of map. odd address data on low byte; even address data on high byte. write_word c8 16-bit address 16-bit data in write to memory with standard bdm ?mware lookup table out of map. must be aligned access. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 457 ?mware. the standard bdm ?mware watches for serial commands and executes them as they are received. the ?mware commands are shown in table 15-6 . 15.4.5 bdm command structure hardware and ?mware bdm commands start with an 8-bit opcode followed by a 16-bit address and/or a 16-bit data word depending on the command. all the read commands return 16 bits of data despite the byte or word implication in the command name. note 8-bit reads return 16-bits of data, of which, only one byte will contain valid data. if reading an even address, the valid data will appear in the msb. if reading an odd address, the valid data will appear in the lsb. table 15-6. firmware commands command 1 1 if enabled, ack will occur when data is ready for transmission for all bdm read commands and will occur after the write is complete for all bdm write commands. opcode (hex) data description read_next 62 16-bit data out increment x by 2 (x = x + 2), then read word x points to. read_pc 63 16-bit data out read program counter. read_d 64 16-bit data out read d accumulator. read_x 65 16-bit data out read x index register. read_y 66 16-bit data out read y index register. read_sp 67 16-bit data out read stack pointer. write_next 42 16-bit data in increment x by 2 (x = x + 2), then write word to location pointed to by x. write_pc 43 16-bit data in write program counter. write_d 44 16-bit data in write d accumulator. write_x 45 16-bit data in write x index register. write_y 46 16-bit data in write y index register. write_sp 47 16-bit data in write stack pointer. go 08 none go to user program. if enabled, ack will occur when leaving active background mode. go_until 2 2 both wait (with clocks to the s12 cpu core disabled) and stop disable the ack function. the go_until command will not get an acknowledge if one of these two cpu instructions occurs before the ?ntil instruction. this can be a problem for any instruction that uses ack, but go_until is a lot more dif?ult for the development tool to time-out. 0c none go to user program. if enabled, ack will occur upon returning to active background mode. trace1 10 none execute one user instruction then return to active bdm. if enabled, ack will occur upon returning to active background mode. taggo 18 none enable tagging and go to user program. there is no ack pulse related to this command. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 458 freescale semiconductor note 16-bit misaligned reads and writes are not allowed. if attempted, the bdm will ignore the least signi?ant bit of the address and will assume an even address from the remaining bits. for hardware data read commands, the external host must wait 150 bus clock cycles after sending the address before attempting to obtain the read data. this is to be certain that valid data is available in the bdm shift register, ready to be shifted out. for hardware write commands, the external host must wait 150 bus clock cycles after sending the data to be written before attempting to send a new command. this is to avoid disturbing the bdm shift register before the write has been completed. the 150 bus clock cycle delay in both cases includes the maximum 128 cycle delay that can be incurred as the bdm waits for a free cycle before stealing a cycle. for ?mware read commands, the external host should wait 44 bus clock cycles after sending the command opcode and before attempting to obtain the read data. this includes the potential of an extra 7 cycles when the access is external with a narrow bus access (+1 cycle) and / or a stretch (+1, 2, or 3 cycles), (7 cycles could be needed if both occur). the 44 cycle wait allows enough time for the requested data to be made available in the bdm shift register, ready to be shifted out. note this timing has increased from previous bdm modules due to the new capability in which the bdm serial interface can potentially run faster than the bus. on previous bdm modules this extra time could be hidden within the serial time. for ?mware write commands, the external host must wait 32 bus clock cycles after sending the data to be written before attempting to send a new command. this is to avoid disturbing the bdm shift register before the write has been completed. the external host should wait 64 bus clock cycles after a trace1 or go command before starting any new serial command. this is to allow the cpu to exit gracefully from the standard bdm ?mware lookup table and resume execution of the user code. disturbing the bdm shift register prematurely may adversely affect the exit from the standard bdm ?mware lookup table. note if the bus rate of the target processor is unknown or could be changing, it is recommended that the ack (acknowledge function) be used to indicate when an operation is complete. when using ack, the delay times are automated. figure 15-6 represents the bdm command structure. the command blocks illustrate a series of eight bit times starting with a falling edge. the bar across the top of the blocks indicates that the bkgd line idles in the high state. the time for an 8-bit command is 8 16 target clock cycles. 1 1. target clock cycles are cycles measured using the target mcu s serial clock rate. see section 15.4.6, ?dm serial interface , and section 15.3.2.1, ?dm status register (bdmsts) , for information on how serial clock rate is selected. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 459 figure 15-6. bdm command structure 15.4.6 bdm serial interface the bdm communicates with external devices serially via the bkgd pin. during reset, this pin is a mode select input which selects between normal and special modes of operation. after reset, this pin becomes the dedicated serial interface pin for the bdm. the bdm serial interface is timed using the clock selected by the clksw bit in the status register see section 15.3.2.1, ?dm status register (bdmsts) . this clock will be referred to as the target clock in the following explanation. the bdm serial interface uses a clocking scheme in which the external host generates a falling edge on the bkgd pin to indicate the start of each bit time. this falling edge is sent for every bit whether data is transmitted or received. data is transferred most signi?ant bit (msb) ?st at 16 target clock cycles per bit. the interface times out if 512 clock cycles occur between falling edges from the host. the bkgd pin is a pseudo open-drain pin and has an weak on-chip active pull-up that is enabled at all times. it is assumed that there is an external pull-up and that drivers connected to bkgd do not typically drive the high level. because r-c rise time could be unacceptably long, the target system and host provide brief driven-high (speedup) pulses to drive bkgd to a logic 1. the source of this speedup pulse is the host for transmit cases and the target for receive cases. the timing for host-to-target is shown in figure 15-7 and that of target-to-host in figure 15-8 and figure 15-9 . all four cases begin when the host drives the bkgd pin low to generate a falling edge. because the host and target are operating from separate clocks, it can take the target system up to one full clock cycle to recognize this edge. the target measures delays from this perceived start of the bit time while the host measures delays from the point it actually drove bkgd low to start the bit up to one target hardware hardware firmware firmware go, 44-bc bc = bus clock cycles command address 150-bc delay next delay 8 bits at 16 tc/bit 16 bits at 16 tc/bit 16 bits at 16 tc/bit command address data next data read write read write trace command next command data 64-bc delay next command 150-bc delay 32-bc delay command command command command data next command tc = target clock cycles chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 460 freescale semiconductor clock cycle earlier. synchronization between the host and target is established in this manner at the start of every bit time. figure 15-7 shows an external host transmitting a logic 1 and transmitting a logic 0 to the bkgd pin of a target system. the host is asynchronous to the target, so there is up to a one clock-cycle delay from the host-generated falling edge to where the target recognizes this edge as the beginning of the bit time. ten target clock cycles later, the target senses the bit level on the bkgd pin. internal glitch detect logic requires the pin be driven high no later that eight target clock cycles after the falling edge for a logic 1 transmission. because the host drives the high speedup pulses in these two cases, the rising edges look like digitally driven signals. figure 15-7. bdm host-to-target serial bit timing the receive cases are more complicated. figure 15-8 shows the host receiving a logic 1 from the target system. because the host is asynchronous to the target, there is up to one clock-cycle delay from the host-generated falling edge on bkgd to the perceived start of the bit time in the target. the host holds the bkgd pin low long enough for the target to recognize it (at least two target clock cycles). the host must release the low drive before the target drives a brief high speedup pulse seven target clock cycles after the perceived start of the bit time. the host should sample the bit level about 10 target clock cycles after it started the bit time. earliest start of next bit target senses bit 10 cycles synchronization uncertainty clock target system host transmit 1 host transmit 0 perceived s tart of bit time chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 461 figure 15-8. bdm target-to-host serial bit timing (logic 1) figure 15-9 shows the host receiving a logic 0 from the target. because the host is asynchronous to the target, there is up to a one clock-cycle delay from the host-generated falling edge on bkgd to the start of the bit time as perceived by the target. the host initiates the bit time but the target ?ishes it. because the target wants the host to receive a logic 0, it drives the bkgd pin low for 13 target clock cycles then brie? drives it high to speed up the rising edge. the host samples the bit level about 10 target clock cycles after starting the bit time. figure 15-9. bdm target-to-host serial bit timing (logic 0) high-impedance earliest start of next bit r-c rise 10 cycles 10 cycles host samples bkgd pin perceived start of bit time bkgd pin clock target system host drive to bkgd pin target system speedup pulse high-impedance high-impedance earliest start of next bit clock target sys. host drive to bkgd pin bkgd pin perceived start of bit time 10 cycles 10 cycles host samples bkgd pin target sys. drive and speedup pulse speedup pulse high-impedance chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 462 freescale semiconductor 15.4.7 serial interface hardware handshake protocol bdm commands that require cpu execution are ultimately treated at the mcu bus rate. because the bdm clock source can be asynchronously related to the bus frequency, when clksw = 0, it is very helpful to provide a handshake protocol in which the host could determine when an issued command is executed by the cpu. the alternative is to always wait the amount of time equal to the appropriate number of cycles at the slowest possible rate the clock could be running. this sub-section will describe the hardware handshake protocol. the hardware handshake protocol signals to the host controller when an issued command was successfully executed by the target. this protocol is implemented by a 16 serial clock cycle low pulse followed by a brief speedup pulse in the bkgd pin. this pulse is generated by the target mcu when a command, issued by the host, has been successfully executed (see figure 15-10 ). this pulse is referred to as the ack pulse. after the ack pulse has ?ished: the host can start the bit retrieval if the last issued command was a read command, or start a new command if the last command was a write command or a control command (background, go, go_until, or trace1). the ack pulse is not issued earlier than 32 serial clock cycles after the bdm command was issued. the end of the bdm command is assumed to be the 16th tick of the last bit. this minimum delay assures enough time for the host to perceive the ack pulse. note also that, there is no upper limit for the delay between the command and the related ack pulse, because the command execution depends upon the cpu bus frequency, which in some cases could be very slow compared to the serial communication rate. this protocol allows a great ?xibility for the pod designers, because it does not rely on any accurate time measurement or short response time to any event in the serial communication. figure 15-10. target acknowledge pulse (ack) note if the ack pulse was issued by the target, the host assumes the previous command was executed. if the cpu enters wait or stop prior to executing a hardware command, the ack pulse will not be issued meaning that the bdm command was not executed. after entering wait or stop mode, the bdm command is no longer pending. 16 cycles bdm clock (target mcu) target transmits pulse ack high-impedance bkgd pin minimum delay from the bdm command 32 cycles earliest start of next bit speedup pulse 16th tick of the last commad bit high-impedance chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 463 figure 15-11 shows the ack handshake protocol in a command level timing diagram. the read_byte instruction is used as an example. first, the 8-bit instruction opcode is sent by the host, followed by the address of the memory location to be read. the target bdm decodes the instruction. a bus cycle is grabbed (free or stolen) by the bdm and it executes the read_byte operation. having retrieved the data, the bdm issues an ack pulse to the host controller, indicating that the addressed byte is ready to be retrieved. after detecting the ack pulse, the host initiates the byte retrieval process. note that data is sent in the form of a word and the host needs to determine which is the appropriate byte based on whether the address was odd or even. figure 15-11. handshake protocol at command level differently from the normal bit transfer (where the host initiates the transmission), the serial interface ack handshake pulse is initiated by the target mcu by issuing a falling edge in the bkgd pin. the hardware handshake protocol in figure 15-10 speci?s the timing when the bkgd pin is being driven, so the host should follow this timing constraint in order to avoid the risk of an electrical con?ct in the bkgd pin. note the only place the bkgd pin can have an electrical con?ct is when one side is driving low and the other side is issuing a speedup pulse (high). other ?ighs are pulled rather than driven. however, at low rates the time of the speedup pulse can become lengthy and so the potential con?ct time becomes longer as well. the ack handshake protocol does not support nested ack pulses. if a bdm command is not acknowledge by an ack pulse, the host needs to abort the pending command ?st in order to be able to issue a new bdm command. when the cpu enters wait or stop while the host issues a command that requires cpu execution (e.g., write_byte), the target discards the incoming command due to the wait or stop being detected. therefore, the command is not acknowledged by the target, which means that the ack pulse will not be issued in this case. after a certain time the host should decide to abort the ack sequence in order to be free to issue a new command. therefore, the protocol should provide a mechanism in which a command, and therefore a pending ack, could be aborted. note differently from a regular bdm command, the ack pulse does not provide a time out. this means that in the case of a wait or stop instruction being executed, the ack would be prevented from being issued. if not aborted, the ack would remain pending inde?itely. see the handshake abort procedure described in section 15.4.8, ?ardware handshake abort procedure . read_byte bdm issues the bkgd pin byte address bdm executes the read_byte command host target host target bdm decodes the command ack pulse (out of scale) host target (2) bytes are retrieved new bdm command chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 464 freescale semiconductor 15.4.8 hardware handshake abort procedure the abort procedure is based on the sync command. in order to abort a command, which had not issued the corresponding ack pulse, the host controller should generate a low pulse in the bkgd pin by driving it low for at least 128 serial clock cycles and then driving it high for one serial clock cycle, providing a speedup pulse. by detecting this long low pulse in the bkgd pin, the target executes the sync protocol, see section 15.4.9, ?ync request timed reference pulse , and assumes that the pending command and therefore the related ack pulse, are being aborted. therefore, after the sync protocol has been completed the host is free to issue new bdm commands. although it is not recommended, the host could abort a pending bdm command by issuing a low pulse in the bkgd pin shorter than 128 serial clock cycles, which will not be interpreted as the sync command. the ack is actually aborted when a falling edge is perceived by the target in the bkgd pin. the short abort pulse should have at least 4 clock cycles keeping the bkgd pin low, in order to allow the falling edge to be detected by the target. in this case, the target will not execute the sync protocol but the pending command will be aborted along with the ack pulse. the potential problem with this abort procedure is when there is a con?ct between the ack pulse and the short abort pulse. in this case, the target may not perceive the abort pulse. the worst case is when the pending command is a read command (i.e., read_byte). if the abort pulse is not perceived by the target the host will attempt to send a new command after the abort pulse was issued, while the target expects the host to retrieve the accessed memory byte. in this case, host and target will run out of synchronism. however, if the command to be aborted is not a read command the short abort pulse could be used. after a command is aborted the target assumes the next falling edge, after the abort pulse, is the ?st bit of a new bdm command. note the details about the short abort pulse are being provided only as a reference for the reader to better understand the bdm internal behavior. it is not recommended that this procedure be used in a real application. because the host knows the target serial clock frequency, the sync command (used to abort a command) does not need to consider the lower possible target frequency. in this case, the host could issue a sync very close to the 128 serial clock cycles length. providing a small overhead on the pulse length in order to assure the sync pulse will not be misinterpreted by the target. see section 15.4.9, ?ync ?request timed reference pulse . figure 15-12 shows a sync command being issued after a read_byte, which aborts the read_byte command. note that, after the command is aborted a new command could be issued by the host computer. note figure 15-12 does not represent the signals in a true timing scale chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 465 figure 15-12. ack abort procedure at the command level figure 15-13 shows a con?ct between the ack pulse and the sync request pulse. this con?ct could occur if a pod device is connected to the target bkgd pin and the target is already in debug active mode. consider that the target cpu is executing a pending bdm command at the exact moment the pod is being connected to the bkgd pin. in this case, an ack pulse is issued along with the sync command. in this case, there is an electrical con?ct between the ack speedup pulse and the sync pulse. because this is not a probable situation, the protocol does not prevent this con?ct from happening. figure 15-13. ack pulse and sync request con?ct note this information is being provided so that the mcu integrator will be aware that such a con?ct could eventually occur. the hardware handshake protocol is enabled by the ack_enable and disabled by the ack_disable bdm commands. this provides backwards compatibility with the existing pod devices which are not able to execute the hardware handshake protocol. it also allows for new pod devices, that support the hardware handshake protocol, to freely communicate with the target device. if desired, without the need for waiting for the ack pulse. read_byte read_status bkgd pin memory address new bdm command new bdm command host target host target host target sync response from the target (out of scale) bdm decode and starts to executes the read_byte cmd read_byte cmd is aborted by the sync request (out of scale) bdm clock (target mcu) target mcu drives to bkgd pin bkgd pin 16 cycles speedup pulse high-impedance host drives sync to bkgd pin ack pulse host sync request pulse at least 128 cycles electrical conflict host and target drive to bkgd pin chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 466 freescale semiconductor the commands are described as follows: ack_enable enables the hardware handshake protocol. the target will issue the ack pulse when a cpu command is executed by the cpu. the ack_enable command itself also has the ack pulse as a response. ack_disable disables the ack pulse protocol. in this case, the host needs to use the worst case delay time at the appropriate places in the protocol. the default state of the bdm after reset is hardware handshake protocol disabled. all the read commands will ack (if enabled) when the data bus cycle has completed and the data is then ready for reading out by the bkgd serial pin. all the write commands will ack (if enabled) after the data has been received by the bdm through the bkgd serial pin and when the data bus cycle is complete. see section 15.4.3, ?dm hardware commands , and section 15.4.4, ?tandard bdm firmware commands , for more information on the bdm commands. the ack_enable sends an ack pulse when the command has been completed. this feature could be used by the host to evaluate if the target supports the hardware handshake protocol. if an ack pulse is issued in response to this command, the host knows that the target supports the hardware handshake protocol. if the target does not support the hardware handshake protocol the ack pulse is not issued. in this case, the ack_enable command is ignored by the target because it is not recognized as a valid command. the background command will issue an ack pulse when the cpu changes from normal to background mode. the ack pulse related to this command could be aborted using the sync command. the go command will issue an ack pulse when the cpu exits from background mode. the ack pulse related to this command could be aborted using the sync command. the go_until command is equivalent to a go command with exception that the ack pulse, in this case, is issued when the cpu enters into background mode. this command is an alternative to the go command and should be used when the host wants to trace if a breakpoint match occurs and causes the cpu to enter active background mode. note that the ack is issued whenever the cpu enters bdm, which could be caused by a breakpoint match or by a bgnd instruction being executed. the ack pulse related to this command could be aborted using the sync command. the trace1 command has the related ack pulse issued when the cpu enters background active mode after one instruction of the application program is executed. the ack pulse related to this command could be aborted using the sync command. the taggo command will not issue an ack pulse because this would interfere with the tagging function shared on the same pin. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 467 15.4.9 sync ?request timed reference pulse the sync command is unlike other bdm commands because the host does not necessarily know the correct communication speed to use for bdm communications until after it has analyzed the response to the sync command. to issue a sync command, the host should perform the following steps: 1. drive the bkgd pin low for at least 128 cycles at the lowest possible bdm serial communication frequency (the lowest serial communication frequency is determined by the crystal oscillator or the clock chosen by clksw.) 2. drive bkgd high for a brief speedup pulse to get a fast rise time (this speedup pulse is typically one cycle of the host clock.) 3. remove all drive to the bkgd pin so it reverts to high impedance. 4. listen to the bkgd pin for the sync response pulse. upon detecting the sync request from the host, the target performs the following steps: 1. discards any incomplete command received or bit retrieved. 2. waits for bkgd to return to a logic 1. 3. delays 16 cycles to allow the host to stop driving the high speedup pulse. 4. drives bkgd low for 128 cycles at the current bdm serial communication frequency. 5. drives a one-cycle high speedup pulse to force a fast rise time on bkgd. 6. removes all drive to the bkgd pin so it reverts to high impedance. the host measures the low time of this 128 cycle sync response pulse and determines the correct speed for subsequent bdm communications. typically, the host can determine the correct communication speed within a few percent of the actual target speed and the communication protocol can easily tolerate speed errors of several percent. as soon as the sync request is detected by the target, any partially received command or bit retrieved is discarded. this is referred to as a soft-reset, equivalent to a time-out in the serial communication. after the sync response, the target will consider the next falling edge (issued by the host) as the start of a new bdm command or the start of new sync request. another use of the sync command pulse is to abort a pending ack pulse. the behavior is exactly the same as in a regular sync command. note that one of the possible causes for a command to not be acknowledged by the target is a host-target synchronization problem. in this case, the command may not have been understood by the target and so an ack response pulse will not be issued. 15.4.10 instruction tracing when a trace1 command is issued to the bdm in active bdm, the cpu exits the standard bdm ?mware and executes a single instruction in the user code. as soon as this has occurred, the cpu is forced to return to the standard bdm ?mware and the bdm is active and ready to receive a new command. if the trace1 command is issued again, the next user instruction will be executed. this facilitates stepping or tracing through the user code one instruction at a time. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 468 freescale semiconductor if an interrupt is pending when a trace1 command is issued, the interrupt stacking operation occurs but no user instruction is executed. upon return to standard bdm ?mware execution, the program counter points to the ?st instruction in the interrupt service routine. 15.4.11 instruction tagging the instruction queue and cycle-by-cycle cpu activity are reconstructible in real time or from trace history that is captured by a logic analyzer. however, the reconstructed queue cannot be used to stop the cpu at a speci? instruction. this is because execution already has begun by the time an operation is visible outside the system. a separate instruction tagging mechanism is provided for this purpose. the tag follows program information as it advances through the instruction queue. when a tagged instruction reaches the head of the queue, the cpu enters active bdm rather than executing the instruction. note tagging is disabled when bdm becomes active and bdm serial commands are not processed while tagging is active. executing the bdm taggo command con?ures two system pins for tagging. the t a glo signal shares a pin with the lstrb signal, and the t a ghi signal shares a pin with the bkgd signal. table 15-7 shows the functions of the two tagging pins. the pins operate independently, that is the state of one pin does not affect the function of the other. the presence of logic level 0 on either pin at the fall of the external clock (eclk) performs the indicated function. high tagging is allowed in all modes. low tagging is allowed only when low strobe is enabled (lstrb is allowed only in wide expanded modes and emulation expanded narrow mode). 15.4.12 serial communication time-out the host initiates a host-to-target serial transmission by generating a falling edge on the bkgd pin. if bkgd is kept low for more than 128 target clock cycles, the target understands that a sync command was issued. in this case, the target will keep waiting for a rising edge on bkgd in order to answer the sync request pulse. if the rising edge is not detected, the target will keep waiting forever without any time-out limit. consider now the case where the host returns bkgd to logic one before 128 cycles. this is interpreted as a valid bit transmission, and not as a sync request. the target will keep waiting for another falling edge marking the start of a new bit. if, however, a new falling edge is not detected by the target within 512 clock cycles since the last falling edge, a time-out occurs and the current command is discarded without affecting memory or the operating mode of the mcu. this is referred to as a soft-reset. table 15-7. tag pin function t a ghi t a glo tag 1 1 no tag 1 0 low byte 0 1 high byte 0 0 both bytes chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 469 if a read command is issued but the data is not retrieved within 512 serial clock cycles, a soft-reset will occur causing the command to be disregarded. the data is not available for retrieval after the time-out has occurred. this is the expected behavior if the handshake protocol is not enabled. however, consider the behavior where the bdc is running in a frequency much greater than the cpu frequency. in this case, the command could time out before the data is ready to be retrieved. in order to allow the data to be retrieved even with a large clock frequency mismatch (between bdc and cpu) when the hardware handshake protocol is enabled, the time out between a read command and the data retrieval is disabled. therefore, the host could wait for more then 512 serial clock cycles and continue to be able to retrieve the data from an issued read command. however, as soon as the handshake pulse (ack pulse) is issued, the time-out feature is re-activated, meaning that the target will time out after 512 clock cycles. therefore, the host needs to retrieve the data within a 512 serial clock cycles time frame after the ack pulse had been issued. after that period, the read command is discarded and the data is no longer available for retrieval. any falling edge of the bkgd pin after the time-out period is considered to be a new command or a sync request. note that whenever a partially issued command, or partially retrieved data, has occurred the time out in the serial communication is active. this means that if a time frame higher than 512 serial clock cycles is observed between two consecutive negative edges and the command being issued or data being retrieved is not complete, a soft-reset will occur causing the partially received command or data retrieved to be disregarded. the next falling edge of the bkgd pin, after a soft-reset has occurred, is considered by the target as the start of a new bdm command, or the start of a sync request pulse. 15.4.13 operation in wait mode the bdm cannot be used in wait mode if the system disables the clocks to the bdm. there is a clearing mechanism associated with the wait instruction when the clocks to the bdm (cpu core platform) are disabled. as the clocks restart from wait mode, the bdm receives a soft reset (clearing any command in progress) and the ack function will be disabled. this is a change from previous bdm modules. 15.4.14 operation in stop mode the bdm is completely shutdown in stop mode. there is a clearing mechanism associated with the stop instruction. stop must be enabled and the part must go into stop mode for this to occur. as the clocks restart from stop mode, the bdm receives a soft reset (clearing any command in progress) and the ack function will be disabled. this is a change from previous bdm modules. chapter 15 background debug module (bdmv4) mc9s12kg128 data sheet, rev. 1.15 470 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 471 chapter 16 debug module (dbgv1) 16.1 introduction this section describes the functionality of the debug (dbg) sub-block of the hcs12 core platform. the dbg module is designed to be fully compatible with the existing bkp_hcs12_a module (bkp mode) and furthermore provides an on-chip trace buffer with ?xible triggering capability (dbg mode). the dbg module provides for non-intrusive debug of application software. the dbg module is optimized for the hcs12 16-bit architecture. 16.1.1 features the dbg module in bkp mode includes these distinctive features: full or dual breakpoint mode compare on address and data (full) compare on either of two addresses (dual) bdm or swi breakpoint enter bdm on breakpoint (bdm) execute swi on breakpoint (swi) tagged or forced breakpoint break just before a speci? instruction will begin execution (tag) break on the ?st instruction boundary after a match occurs (force) single, range, or page address compares compare on address (single) compare on address 256 byte (range) compare on any 16k page (page) at forced breakpoints compare address on read or write high and/or low byte data compares comparator c can provide an additional tag or force breakpoint (enhancement for bkp mode) chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 472 freescale semiconductor the dbg in dbg mode includes these distinctive features: three comparators (a, b, and c) dual mode, comparators a and b used to compare addresses full mode, comparator a compares address and comparator b compares data can be used as trigger and/or breakpoint comparator c used in loop1 capture mode or as additional breakpoint four capture modes normal mode, change-of-?w information is captured based on trigger speci?ation loop1 mode, comparator c is dynamically updated to prevent redundant change-of-?w storage. detail mode, address and data for all cycles except program fetch (p) and free (f) cycles are stored in trace buffer pro?e mode, last instruction address executed by cpu is returned when trace buffer address is read two types of breakpoint or debug triggers break just before a speci? instruction will begin execution (tag) break on the ?st instruction boundary after a match occurs (force) bdm or swi breakpoint enter bdm on breakpoint (bdm) execute swi on breakpoint (swi) nine trigger modes for comparators a and b ? a or b a then b a and b, where b is data (full mode) a and not b, where b is data (full mode) event only b, store data a then event only b, store data inside range, a address b outside range, address < or address > b comparator c provides an additional tag or force breakpoint when capture mode is not con?ured in loop1 mode. sixty-four word (16 bits wide) trace buffer for storing change-of-?w information, event only data and other bus information. source address of taken conditional branches (long, short, bit-conditional, and loop constructs) destination address of indexed jmp, jsr, and call instruction. destination address of rti, rts, and rtc instructions vector address of interrupts, except for swi and bdm vectors chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 473 data associated with event b trigger modes detail report mode stores address and data for all cycles except program (p) and free (f) cycles current instruction address when in pro?ing mode bgnd is not considered a change-of-?w (cof) by the debugger 16.1.2 modes of operation there are two main modes of operation: breakpoint mode and debug mode. each one is mutually exclusive of the other and selected via a software programmable control bit. in the breakpoint mode there are two sub-modes of operation: dual address mode, where a match on either of two addresses will cause the system to enter background debug mode (bdm) or initiate a software interrupt (swi). full breakpoint mode, where a match on address and data will cause the system to enter background debug mode (bdm) or initiate a software interrupt (swi). in debug mode, there are several sub-modes of operation. trigger modes there are many ways to create a logical trigger. the trigger can be used to capture bus information either starting from the trigger or ending at the trigger. types of triggers (a and b are registers): a only a or b a then b event only b (data capture) a then event only b (data capture) a and b, full mode a and not b, full mode inside range outside range capture modes there are several capture modes. these determine which bus information is saved and which is ignored. normal: save change-of-?w program fetches loop1: save change-of-?w program fetches, ignoring duplicates detail: save all bus operations except program and free cycles pro?e: poll target from external device 16.1.3 block diagram figure 16-1 is a block diagram of this module in breakpoint mode. figure 16-2 is a block diagram of this module in debug mode. chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 474 freescale semiconductor figure 16-1. dbg block diagram in bkp mode comparator compare block register block comparator comparator comparator comparator comparator expansion addresses expansion addresses address high address low data high data low address high address low comparator comparator read data high read data low . . . . . . . . . . . . clocks and bkp control control signals signals control block breakpoint modes and generation of swi, force bdm, and tags expansion address address write data read data read/write control control bits control signals results signals bkp0h bkp0l bkp0x bkpct0 bkp1x bkpct1 bkp1l bkp1h write bkp read data bus data bus data/address high mux data/address low mux chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 475 figure 16-2. dbg block diagram in dbg mode 16.2 external signal description the dbg sub-module relies on the external bus interface (generally the mebi) when the dbg is matching on the external bus. the tag pins in table 16-1 (part of the mebi) may also be a part of the breakpoint operation. table 16-1. external system pins associated with dbg and mebi pin name pin functions description bkgd/modc/ t a ghi t a ghi when instruction tagging is on, a 0 at the falling edge of e tags the high half of the instruction word being read into the instruction queue. pe3/ lstrb/ t a glo t a glo in expanded wide mode or emulation narrow modes, when instruction tagging is on and low strobe is enabled, a 0 at the falling edge of e tags the low half of the instruction word being read into the instruction queue. tag force address bus match_a control read data bus read/write store mcu in bdm m u x pointer register match_b m u x event only write data bus trace buffer dbg read data bus dbg mode enable m u x write data bus read data bus read/write match_c loop1 detail m u x profile capture mode cpu program counter control comparator a address/data/control comparator b comparator c registers tracer buffer control logic change-of-flow indicators or profiling data 64 x 16 bit word trace buffer profile capture register last instruction address bus clock instruction last cycle chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 476 freescale semiconductor 16.3 memory map and register de?ition a summary of the registers associated with the dbg sub-block is shown in figure 16-3 . detailed descriptions of the registers and bits are given in the subsections that follow. 16.3.1 module memory map 16.3.2 register descriptions this section consists of the dbg register descriptions in address order. most of the register bits can be written to in either bkp or dbg mode, although they may not have any effect in one of the modes. however, the only bits in the dbg module that can be written while the debugger is armed (arm = 1) are dbgen and arm table 16-2. dbg memory map address offset use access debug control register (dbgc1) r/w debug status and control register (dbgsc) r/w debug trace buffer register high (dbgtbh) r debug trace buffer register low (dbgtbl) r 4 debug count register (dbgcnt) r 5 debug comparator c extended register (dbgccx) r/w 6 debug comparator c register high (dbgcch) r/w debug comparator c register low (dbgccl) r/w 8 debug control register 2 (dbgc2) / (bkpct0) r/w 9 debug control register 3 (dbgc3) / (bkpct1) r/w a debug comparator a extended register (dbgcax) / (/bkp0x) r/w b debug comparator a register high (dbgcah) / (bkp0h) r/w debug comparator a register low (dbgcal) / (bkp0l) r/w debug comparator b extended register (dbgcbx) / (bkp1x) r/w e debug comparator b register high (dbgcbh) / (bkp1h) r/w f debug comparator b register low (dbgcbl) / (bkp1l) r/w name 1 bit 7 6 5 4 3 2 1 bit 0 dbgc1 r dbgen arm trgsel begin dbgbrk 0 capmod w dbgsc raf bf cf 0 trg w = unimplemented or reserved figure 16-3. dbg register summary chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 477 dbgtbh r bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 w dbgtbl r bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 w dbgcnt r tbf 0 cnt w dbgccx (2 ) r pagsel extcmp w dbgcch (2) r bit 15 14 13 12 11 10 9 bit 8 w dbgccl (2) r bit 7 6 5 4 3 2 1 bit 0 w dbgc2 bkpct0 r bkaben full bdm tagab bkcen tagc rwcen rwc w dbgc3 bkpct1 r bkambh bkambl bkbmbh bkbmbl rwaen rwa rwben rwb w dbgcax bkp0x r pagsel extcmp w dbgcah bkp0h r bit 15 14 13 12 11 10 9 bit 8 w dbgcal bkp0l r bit 7 6 5 4 3 2 1 bit 0 w dbgcbx bkp1x r pagsel extcmp w dbgcbh bkp1h r bit 15 14 13 12 11 10 9 bit 8 w dbgcbl bkp1l r bit 7 6 5 4 3 2 1 bit 0 w 1 the dbg module is designed for backwards compatibility to existing bkp modules. register and bit names have changed from the bkp module. this column shows the dbg register name, as well as the bkp register name for reference. 2 comparator c can be used to enhance the bkp mode by providing a third breakpoint. name 1 bit 7 6 5 4 3 2 1 bit 0 = unimplemented or reserved figure 16-3. dbg register summary (continued) chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 478 freescale semiconductor 16.3.2.1 debug control register 1 (dbgc1) note all bits are used in dbg mode only. note this register cannot be written if bkp mode is enabled (bkaben in dbgc2 is set). 76543210 r dbgen arm trgsel begin dbgbrk 0 capmod w reset 0 0 0 00000 = unimplemented or reserved figure 16-4. debug control register (dbgc1) table 16-3. dbgc1 field descriptions field description 7 dbgen dbg mode enable bit ?the dbgen bit enables the dbg module for use in dbg mode. this bit cannot be set if the mcu is in secure mode. 0 dbg mode disabled 1 dbg mode enabled 6 arm arm bit ?the arm bit controls whether the debugger is comparing and storing data in the trace buffer. see section 16.4.2.4, ?rming the dbg module , for more information. 0 debugger unarmed 1 debugger armed note: this bit cannot be set if the dbgen bit is not also being set at the same time. for example, a write of 01 to dbgen[7:6] will be interpreted as a write of 00. 5 trgsel trigger selection bit ?the trgsel bit controls the triggering condition for comparators a and b in dbg mode. it serves essentially the same function as the tagab bit in the dbgc2 register does in bkp mode. see section 16.4.2.1.2, ?rigger selection , for more information. trgsel may also determine the type of breakpoint based on comparator a and b if enabled in dbg mode (dbgbrk = 1). please refer to section 16.4.3.1, ?reakpoint based on comparator a and b . 0 trigger on any compare address match 1 trigger before opcode at compare address gets executed (tagged-type) 4 begin begin/end trigger bit the begin bit controls whether the trigger begins or ends storing of data in the trace buffer. see section 16.4.2.8.1, ?toring with begin-trigger , and section 16.4.2.8.2, ?toring with end-trigger , for more details. 0 trigger at end of stored data 1 trigger before storing data chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 479 3 dbgbrk dbg breakpoint enable bit the dbgbrk bit controls whether the debugger will request a breakpoint based on comparator a and b to the cpu upon completion of a tracing session. please refer to section 16.4.3, ?reakpoints , for further details. 0 cpu break request not enabled 1 cpu break request enabled 1:0 capmod capture mode field ?see table 16-4 for capture mode ?ld de?itions. in loop1 mode, the debugger will automatically inhibit redundant entries into capture memory. in detail mode, the debugger is storing address and data for all cycles except program fetch (p) and free (f) cycles. in pro?e mode, the debugger is returning the address of the last instruction executed by the cpu on each access of trace buffer address. refer to section 16.4.2.6, ?apture modes , for more information. table 16-4. capmod encoding capmod description 00 normal 01 loop1 10 detail 11 profile table 16-3. dbgc1 field descriptions (continued) field description chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 480 freescale semiconductor 16.3.2.2 debug status and control register (dbgsc) 76543210 raf bf cf 0 trg w reset 0 0 0 00000 = unimplemented or reserved figure 16-5. debug status and control register (dbgsc) table 16-5. dbgsc field descriptions field description 7 af trigger a match flag ?the af bit indicates if trigger a match condition was met since arming. this bit is cleared when arm in dbgc1 is written to a 1 or on any write to this register. 0 trigger a did not match 1 trigger a match 6 bf trigger b match flag ?the bf bit indicates if trigger b match condition was met since arming.this bit is cleared when arm in dbgc1 is written to a 1 or on any write to this register. 0 trigger b did not match 1 trigger b match 5 cf comparator c match flag the cf bit indicates if comparator c match condition was met since arming.this bit is cleared when arm in dbgc1 is written to a 1 or on any write to this register. 0 comparator c did not match 1 comparator c match 3:0 trg trigger mode bits ?the trg bits select the trigger mode of the dbg module as shown table 16-6 . see section 16.4.2.5, ?rigger modes , for more detail. table 16-6. trigger mode encoding trg value meaning 0000 a only 0001 a or b 0010 a then b 0011 event only b 0100 a then event only b 0101 a and b (full mode) 0110 a and not b (full mode) 0111 inside range 1000 outside range 1001 1111 reserved (defaults to a only) chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 481 16.3.2.3 debug trace buffer register (dbgtb) 15 14 13 12 11 10 9 8 r bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 w reset u u u uuuuu = unimplemented or reserved figure 16-6. debug trace buffer register high (dbgtbh) 76543210 r bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 w reset u u u uuuuu = unimplemented or reserved figure 16-7. debug trace buffer register low (dbgtbl) table 16-7. dbgtb field descriptions field description 15:0 trace buffer data bits the trace buffer data bits contain the data of the trace buffer. this register can be read only as a word read. any byte reads or misaligned access of these registers will return 0 and will not cause the trace buffer pointer to increment to the next trace buffer address. the same is true for word reads while the debugger is armed. in addition, this register may appear to contain incorrect data if it is not read with the same capture mode bit settings as when the trace buffer data was recorded (see section 16.4.2.9, ?eading data from trace buffer ?. because reads will re?ct the contents of the trace buffer ram, the reset state is unde?ed. chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 482 freescale semiconductor 16.3.2.4 debug count register (dbgcnt) 76543210 r tbf 0 cnt w reset 0 0 0 00000 = unimplemented or reserved figure 16-8. debug count register (dbgcnt) table 16-8. dbgcnt field descriptions field description 7 tbf trace buffer full the tbf bit indicates that the trace buffer has stored 64 or more words of data since it was last armed. if this bit is set, then all 64 words will be valid data, regardless of the value in cnt[5:0]. the tbf bit is cleared when arm in dbgc1 is written to a 1. 5:0 cnt count value the cnt bits indicate the number of valid data words stored in the trace buffer. table 16-9 shows the correlation between the cnt bits and the number of valid data words in the trace buffer. when the cnt rolls over to 0, the tbf bit will be set and incrementing of cnt will continue if dbg is in end-trigger mode. the dbgcnt register is cleared when arm in dbgc1 is written to a 1. table 16-9. cnt decoding table tbf cnt description 0 000000 no data valid 0 000001 1 word valid 0 000010 .. .. 111110 2 words valid .. .. 62 words valid 0 111111 63 words valid 1 000000 64 words valid; if begin = 1, the arm bit will be cleared. a breakpoint will be generated if dbgbrk = 1 1 000001 .. .. 111111 64 words valid, oldest data has been overwritten by most recent data chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 483 16.3.2.5 debug comparator c extended register (dbgccx) 76543210 r pagsel extcmp w reset 0 0 0 00000 figure 16-9. debug comparator c extended register (dbgccx) table 16-10. dbgccx field descriptions field description 7:6 pagsel page selector field ?in both bkp and dbg mode, pagsel selects the type of paging as shown in table 16-11 . dpage and epage are not yet implemented so the value in bit 7 will be ignored (i.e., pagsel values of 10 and 11 will be interpreted as values of 00 and 01, respectively). 5:0 extcmp comparator c extended compare bits the extcmp bits are used as comparison address bits as shown in table 16-11 along with the appropriate ppage, dpage, or epage signal from the core. note: comparator c can be used when the dbg module is con?ured for bkp mode. extended addressing comparisons for comparator c use pagsel and will operate differently to the way that comparator a and b operate in bkp mode. table 16-11. pagsel decoding 1 1 see figure 16-10 . pagsel description extcmp comment 00 normal (64k) not used no paged memory 01 ppage (256 ?16k pages) extcmp[5:0] is compared to address bits [21:16] 2 2 current hcs12 implementations have ppage limited to 6 bits. therefore, extcmp[5:4] should be set to 00. ppage[7:0] / xab[21:14] becomes address bits [21:14] 1 10 3 3 data page (dpage) and extra page (epage) are reserved for implementation on devices that support paged data and extra space. dpage (reserved) (256 ?4k pages) extcmp[3:0] is compared to address bits [19:16] dpage / xab[21:14] becomes address bits [19:12] 11 2 epage (reserved) (256 ?1k pages) extcmp[1:0] is compared to address bits [17:16] epage / xab[21:14] becomes address bits [17:10] chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 484 freescale semiconductor 16.3.2.6 debug comparator c register (dbgcc) dbgcxx dbgcxh[15:12] pagsel extcmp bit 15 bit 14 bit 13 bit 12 76 0 5 0 4 3 2 1 bit 0 see note 1 portk/xab xab21 xab20 xab19 xab18 xab17 xab16 xab15 xab14 ppage pix7 pix6 pix5 pix4 pix3 pix2 pix1 pix0 see note 2 notes: 1. in bkp and dbg mode, pagsel selects the type of paging as shown in table 16-11 . 2. current hcs12 implementations are limited to six ppage bits, pix[5:0]. therefore, extcmp[5:4] = 00. figure 16-10. comparator c extended comparison in bkp/dbg mode 15 14 13 12 11 10 9 8 r bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 w reset 0 0 0 00000 = unimplemented or reserved figure 16-11. debug comparator c register high (dbgcch) 76543210 r bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 w reset 0 0 0 00000 = unimplemented or reserved figure 16-12. debug comparator c register low (dbgccl) table 16-12. dbgcc field descriptions field description 15:0 comparator c compare bits ?the comparator c compare bits control whether comparator c will compare the address bus bits [15:0] to a logic 1 or logic 0. see table 16-13 . 0 compare corresponding address bit to a logic 0 1 compare corresponding address bit to a logic 1 note: this register will be cleared automatically when the dbg module is armed in loop1 mode. bkp/dbg mode chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 485 16.3.2.7 debug control register 2 (dbgc2) figure 16-13. debug control register 2 (dbgc2) table 16-13. comparator c compares pagsel extcmp compare high-byte compare x0 no compare dbgcch[7:0] = ab[15:8] x1 extcmp[5:0] = xab[21:16] dbgcch[7:0] = xab[15:14],ab[13:8] 76543210 r bkaben 1 1 when bkaben is set (bkp mode), all bits in dbgc2 are available. when bkaben is cleared and dbg is used in dbg mode, bits full and tagab have no meaning. full bdm tagab bkcen 2 2 these bits can be used in bkp mode and dbg mode (when capture mode is not set in loop1) to provide a third breakpoint. tag c 2 rwcen 2 rwc 2 w reset 0 0 0 00000 table 16-14. dbgc2 field descriptions field description 7 bkaben breakpoint using comparator a and b enable this bit enables the breakpoint capability using comparator a and b, when set (bkp mode) the dbgen bit in dbgc1 cannot be set. 0 breakpoint module off 1 breakpoint module on 6 full full breakpoint mode enable this bit controls whether the breakpoint module is in dual mode or full mode. in full mode, comparator a is used to match address and comparator b is used to match data. see section 16.4.1.2, ?ull breakpoint mode , for more details. 0 dual address mode enabled 1 full breakpoint mode enabled 5 bdm background debug mode enable ?this bit determines if the breakpoint causes the system to enter background debug mode (bdm) or initiate a software interrupt (swi). 0 go to software interrupt on a break request 1 go to bdm on a break request 4 tagab comparator a/b tag select this bit controls whether the breakpoint will cause a break on the next instruction boundary (force) or on a match that will be an executable opcode (tagged). non-executed opcodes cannot cause a tagged breakpoint. 0 on match, break at the next instruction boundary (force) 1 on match, break if/when the instruction is about to be executed (tagged) 3 bkcen breakpoint comparator c enable bit ?this bit enables the breakpoint capability using comparator c. 0 comparator c disabled for breakpoint 1 comparator c enabled for breakpoint note: this bit will be cleared automatically when the dbg module is armed in loop1 mode. 2 tag c comparator c tag select this bit controls whether the breakpoint will cause a break on the next instruction boundary (force) or on a match that will be an executable opcode (tagged). non-executed opcodes cannot cause a tagged breakpoint. 0 on match, break at the next instruction boundary (force) 1 on match, break if/when the instruction is about to be executed (tagged) chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 486 freescale semiconductor 16.3.2.8 debug control register 3 (dbgc3) figure 16-14. debug control register 3 (dbgc3) 1 rwcen read/write comparator c enable bit the rwcen bit controls whether read or write comparison is enabled for comparator c. rwcen is not useful for tagged breakpoints. 0 read/write is not used in comparison 1 read/write is used in comparison 0 rwc read/write comparator c value bit ?the rwc bit controls whether read or write is used in compare for comparator c. the rwc bit is not used if rwcen = 0. 0 write cycle will be matched 1 read cycle will be matched 76543210 r bkambh 1 1 in dbg mode, bkambh:bkambl has no meaning and are forced to 0 s. bkambl 1 bkbmbh 2 2 in dbg mode, bkbmbh:bkbmbl are used in full mode to qualify data. bkbmbl 2 rwaen rwa rwben rwb w reset 0 0 0 00000 table 16-15. dbgc3 field descriptions field description 7:6 bkamb[h:l] breakpoint mask high byte for first address in dual or full mode, these bits may be used to mask (disable) the comparison of the high and/or low bytes of the ?st address breakpoint. the functionality is as given in table 16-16 . the x:0 case is for a full address compare. when a program page is selected, the full address compare will be based on bits for a 20-bit compare. the registers used for the compare are {dbgcax[5:0], dbgcah[5:0], dbgcal[7:0]}, where dbgax[5:0] corresponds to ppage[5:0] or extended address bits [19:14] and cpu address [13:0]. when a program page is not selected, the full address compare will be based on bits for a 16-bit compare. the registers used for the compare are {dbgcah[7:0], dbgcal[7:0]} which corresponds to cpu address [15:0]. note: this extended address compare scheme causes an aliasing problem in bkp mode in which several physical addresses may match with a single logical address. this problem may be avoided by using dbg mode to generate breakpoints. the 1:0 case is not sensible because it would ignore the high order address and compare the low order and expansion addresses. logic forces this case to compare all address lines (effectively ignoring the bkambh control bit). the 1:1 case is useful for triggering a breakpoint on any access to a particular expansion page. this only makes sense if a program page is being accessed so that the breakpoint trigger will occur only if dbgcax compares. table 16-14. dbgc2 field descriptions (continued) field description chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 487 5:4 bkbmb[h:l] breakpoint mask high byte and low byte of data (second address) ?in dual mode, these bits may be used to mask (disable) the comparison of the high and/or low bytes of the second address breakpoint. the functionality is as given in table 16-17 . the x:0 case is for a full address compare. when a program page is selected, the full address compare will be based on bits for a 20-bit compare. the registers used for the compare are {dbgcbx[5:0], dbgcbh[5:0], dbgcbl[7:0]} where dbgcbx[5:0] corresponds to ppage[5:0] or extended address bits [19:14] and cpu address [13:0]. when a program page is not selected, the full address compare will be based on bits for a 16-bit compare. the registers used for the compare are {dbgcbh[7:0], dbgcbl[7:0]} which corresponds to cpu address [15:0]. note: this extended address compare scheme causes an aliasing problem in bkp mode in which several physical addresses may match with a single logical address. this problem may be avoided by using dbg mode to generate breakpoints. the 1:0 case is not sensible because it would ignore the high order address and compare the low order and expansion addresses. logic forces this case to compare all address lines (effectively ignoring the bkbmbh control bit). the 1:1 case is useful for triggering a breakpoint on any access to a particular expansion page. this only makes sense if a program page is being accessed so that the breakpoint trigger will occur only if dbgcbx compares. in full mode, these bits may be used to mask (disable) the comparison of the high and/or low bytes of the data breakpoint. the functionality is as given in table 16-18 . 3 rwaen read/write comparator a enable bit the rwaen bit controls whether read or write comparison is enabled for comparator a. see section 16.4.2.1.1, ?ead or write comparison , for more information. this bit is not useful for tagged operations. 0 read/write is not used in comparison 1 read/write is used in comparison 2 rwa read/write comparator a value bit ?the rwa bit controls whether read or write is used in compare for comparator a. the rwa bit is not used if rwaen = 0. 0 write cycle will be matched 1 read cycle will be matched 1 rwben read/write comparator b enable bit the rwben bit controls whether read or write comparison is enabled for comparator b. see section 16.4.2.1.1, ?ead or write comparison , for more information. this bit is not useful for tagged operations. 0 read/write is not used in comparison 1 read/write is used in comparison 0 rwb read/write comparator b value bit ?the rwb bit controls whether read or write is used in compare for comparator b. the rwb bit is not used if rwben = 0. 0 write cycle will be matched 1 read cycle will be matched note: rwb and rwben are not used in full mode. table 16-16. breakpoint mask bits for first address bkambh:bkambl address compare dbgcax dbgcah dbgcal x:0 full address compare yes 1 1 if ppage is selected. ye s ye s 0:1 256 byte address range yes 1 ye s n o 1:1 16k byte address range yes 1 no no table 16-15. dbgc3 field descriptions (continued) field description chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 488 freescale semiconductor table 16-17. breakpoint mask bits for second address (dual mode) bkbmbh:bkbmbl address compare dbgcbx dbgcbh dbgcbl x:0 full address compare yes 1 1 if ppage is selected. ye s ye s 0:1 256 byte address range yes 1 ye s n o 1:1 16k byte address range yes 1 no no table 16-18. breakpoint mask bits for data breakpoints (full mode) bkbmbh:bkbmbl data compare dbgcbx dbgcbh dbgcbl 0:0 high and low byte compare no 1 1 expansion addresses for breakpoint b are not applicable in this mode. ye s ye s 0:1 high byte no 1 ye s n o 1:0 low byte no 1 no yes 1:1 no compare no 1 no no chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 489 16.3.2.9 debug comparator a extended register (dbgcax) 76543210 r pagsel extcmp w reset 0 0 0 00000 figure 16-15. debug comparator a extended register (dbgcax) table 16-19. dbgcax field descriptions field description 7:6 pagsel page selector field ?if dbgen is set in dbgc1, then pagsel selects the type of paging as shown in table 16-20 . dpage and epage are not yet implemented so the value in bit 7 will be ignored (i.e., pagsel values of 10 and 11 will be interpreted as values of 00 and 01, respectively). in bkp mode, pagsel has no meaning and extcmp[5:0] are compared to address bits [19:14] if the address is in the flash/rom memory space. 5:0 extcmp comparator a extended compare bits the extcmp bits are used as comparison address bits as shown in table 16-20 along with the appropriate ppage, dpage, or epage signal from the core. table 16-20. comparator a or b compares mode extcmp compare high-byte compare bkp 1 1 see figure 16-16 . not flash/rom access no compare dbgcxh[7:0] = ab[15:8] flash/rom access extcmp[5:0] = xab[19:14] dbgcxh[5:0] = ab[13:8] dbg 2 2 see figure 16-10 (note that while this ?ure provides extended comparisons for comparator c, the ?ure also pertains to comparators a and b in dbg mode only). pagsel = 00 no compare dbgcxh[7:0] = ab[15:8] pagsel = 01 extcmp[5:0] = xab[21:16] dbgcxh[7:0] = xab[15:14], ab[13:8] pagsel extcmp dbgcxx 0 0 54321 bit 0 see note 1 portk/xab xab21 xab20 xab19 xab18 xab17 xab16 xab15 xab14 ppage pix7 pix6 pix5 pix4 pix3 pix2 pix1 pix0 see note 2 notes: 1. in bkp mode, pagsel has no functionality. therefore, set pagsel to 00 (reset state). 2. current hcs12 implementations are limited to six ppage bits, pix[5:0]. figure 16-16. comparators a and b extended comparison in bkp mode bkp mode chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 490 freescale semiconductor 16.3.2.10 debug comparator a register (dbgca) 16.3.2.11 debug comparator b extended register (dbgcbx) 15 14 13 12 11 10 9 8 r bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 w reset 0 0 0 00000 figure 16-17. debug comparator a register high (dbgcah) 76543210 r bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 w reset 0 0 0 00000 figure 16-18. debug comparator a register low (dbgcal) table 16-21. dbgca field descriptions field description 15:0 15:0 comparator a compare bits the comparator a compare bits control whether comparator a compares the address bus bits [15:0] to a logic 1 or logic 0. see table 16-20 . 0 compare corresponding address bit to a logic 0 1 compare corresponding address bit to a logic 1 76543210 r pagsel extcmp w reset 0 0 0 00000 figure 16-19. debug comparator b extended register (dbgcbx) table 16-22. dbgcbx field descriptions field description 7:6 pagsel page selector field ?if dbgen is set in dbgc1, then pagsel selects the type of paging as shown in table 16-11 . dpage and epage are not yet implemented so the value in bit 7 will be ignored (i.e., pagsel values of 10 and 11 will be interpreted as values of 00 and 01, respectively.) in bkp mode, pagsel has no meaning and extcmp[5:0] are compared to address bits [19:14] if the address is in the flash/rom memory space. 5:0 extcmp comparator b extended compare bits the extcmp bits are used as comparison address bits as shown in table 16-11 along with the appropriate ppage, dpage, or epage signal from the core. also see table 16-20 . chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 491 16.3.2.12 debug comparator b register (dbgcb) 16.4 functional description this section provides a complete functional description of the dbg module. the dbg module can be con?ured to run in either of two modes, bkp or dbg. bkp mode is enabled by setting bkaben in dbgc2. dbg mode is enabled by setting dbgen in dbgc1. setting bkaben in dbgc2 overrides the dbgen in dbgc1 and prevents dbg mode. if the part is in secure mode, dbg mode cannot be enabled. 16.4.1 dbg operating in bkp mode in bkp mode, the dbg will be fully backwards compatible with the existing bkp_st12_a module. the dbgc2 register has four additional bits that were not available on existing bkp_st12_a modules. as long as these bits are written to either all 1s or all 0s, they should be transparent to the user. all 1s would enable comparator c to be used as a breakpoint, but tagging would be enabled. the match address register would be all 0s if not modi?d by the user. therefore, code executing at address 0x0000 would have to occur before a breakpoint based on comparator c would happen. the dbg module in bkp mode supports two modes of operation: dual address mode and full breakpoint mode. within each of these modes, forced or tagged breakpoint types can be used. forced breakpoints occur at the next instruction boundary if a match occurs and tagged breakpoints allow for breaking just before the tagged instruction executes. the action taken upon a successful match can be to either place the cpu in background debug mode or to initiate a software interrupt. 15 14 13 12 11 10 9 8 r bit 15 bit 14 bit 13 bit 12 bit 11 bit 10 bit 9 bit 8 w reset 0 0 0 00000 figure 16-20. debug comparator b register high (dbgcbh) 76543210 r bit 7 bit 6 bit 5 bit 4 bit 3 bit 2 bit 1 bit 0 w reset 0 0 0 00000 figure 16-21. debug comparator b register low (dbgcbl) table 16-23. dbgcb field descriptions field description 15:0 15:0 comparator b compare bits the comparator b compare bits control whether comparator b compares the address bus bits [15:0] or data bus bits [15:0] to a logic 1 or logic 0. see table 16-20 . 0 compare corresponding address bit to a logic 0, compares to data if in full mode 1 compare corresponding address bit to a logic 1, compares to data if in full mode chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 492 freescale semiconductor the breakpoint can operate in dual address mode or full breakpoint mode. each of these modes is discussed in the subsections below. 16.4.1.1 dual address mode when dual address mode is enabled, two address breakpoints can be set. each breakpoint can cause the system to enter background debug mode or to initiate a software interrupt based upon the state of bdm in dbgc2 being logic 1 or logic 0, respectively. bdm requests have a higher priority than swi requests. no data breakpoints are allowed in this mode. tagab in dbgc2 selects whether the breakpoint mode is forced or tagged. the bkxmbh:l bits in dbgc3 select whether or not the breakpoint is matched exactly or is a range breakpoint. they also select whether the address is matched on the high byte, low byte, both bytes, and/or memory expansion. the rwx and rwxen bits in dbgc3 select whether the type of bus cycle to match is a read, write, or read/write when performing forced breakpoints. 16.4.1.2 full breakpoint mode full breakpoint mode requires a match on address and data for a breakpoint to occur. upon a successful match, the system will enter background debug mode or initiate a software interrupt based upon the state of bdm in dbgc2 being logic 1 or logic 0, respectively. bdm requests have a higher priority than swi requests. r/w matches are also allowed in this mode. tagab in dbgc2 selects whether the breakpoint mode is forced or tagged. when tagab is set in dbgc2, only addresses are compared and data is ignored. the bkambh:l bits in dbgc3 select whether or not the breakpoint is matched exactly, is a range breakpoint, or is in page space. the bkbmbh:l bits in dbgc3 select whether the data is matched on the high byte, low byte, or both bytes. rwa and rwaen bits in dbgc2 select whether the type of bus cycle to match is a read or a write when performing forced breakpoints. rwb and rwben bits in dbgc2 are not used in full breakpoint mode. note the full trigger mode is designed to be used for either a word access or a byte access, but not both at the same time. confusing trigger operation (seemingly false triggers or no trigger) can occur if the trigger address occurs in the user program as both byte and word accesses. 16.4.1.3 breakpoint priority breakpoint operation is ?st determined by the state of the bdm module. if the bdm module is already active, meaning the cpu is executing out of bdm ?mware, breakpoints are not allowed. in addition, while executing a bdm trace command, tagging into bdm is not allowed. if bdm is not active, the breakpoint will give priority to bdm requests over swi requests. this condition applies to both forced and tagged breakpoints. in all cases, bdm related breakpoints will have priority over those generated by the breakpoint sub-block. this priority includes breakpoints enabled by the t a glo and t a ghi external pins of the system that interface with the bdm directly and whose signal information passes through and is used by the breakpoint sub-block. chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 493 note bdm should not be entered from a breakpoint unless the enable bit is set in the bdm. even if the enable bit in the bdm is cleared, the cpu actually executes the bdm ?mware code. it checks the enable and returns if enable is not set. if the bdm is not serviced by the monitor then the breakpoint would be re-asserted when the bdm returns to normal cpu ?w. there is no hardware to enforce restriction of breakpoint operation if the bdm is not enabled. when program control returns from a tagged breakpoint through an rti or a bdm go command, it will return to the instruction whose tag generated the breakpoint. unless breakpoints are disabled or modi?d in the service routine or active bdm session, the instruction will be tagged again and the breakpoint will be repeated. in the case of bdm breakpoints, this situation can also be avoided by executing a trace1 command before the go to increment the program ?w past the tagged instruction. 16.4.1.4 using comparator c in bkp mode the original bkp_st12_a module supports two breakpoints. the dbg_st12_a module can be used in bkp mode and allow a third breakpoint using comparator c. four additional bits, bkcen, tagc, rwcen, and rwc in dbgc2 in conjunction with additional comparator c address registers, dbgccx, dbgcch, and dbgccl allow the user to set up a third breakpoint. using pagsel in dbgccx for expanded memory will work differently than the way paged memory is done using comparator a and b in bkp mode. see section 16.3.2.5, ?ebug comparator c extended register (dbgccx) , for more information on using comparator c. 16.4.2 dbg operating in dbg mode enabling the dbg module in dbg mode, allows the arming, triggering, and storing of data in the trace buffer and can be used to cause cpu breakpoints. the dbg module is made up of three main blocks, the comparators, trace buffer control logic, and the trace buffer. note in general, there is a latency between the triggering event appearing on the bus and being detected by the dbg circuitry. in general, tagged triggers will be more predictable than forced triggers. 16.4.2.1 comparators the dbg contains three comparators, a, b, and c. comparator a compares the core address bus with the address stored in dbgcah and dbgcal. comparator b compares the core address bus with the address stored in dbgcbh and dbgcbl except in full mode, where it compares the data buses to the data stored in dbgcbh and dbgcbl. comparator c can be used as a breakpoint generator or as the address comparison unit in the loop1 mode. matches on comparator a, b, and c are signaled to the trace buffer chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 494 freescale semiconductor control (tbc) block. when pagsel = 01, registers dbgcax, dbgcbx, and dbgccx are used to match the upper addresses as shown in table 16-11 . note if a tagged-type c breakpoint is set at the same address as an a/b tagged-type trigger (including the initial entry in an inside or outside range trigger), the c breakpoint will have priority and the trigger will not be recognized. 16.4.2.1.1 read or write comparison read or write comparisons are useful only with trgsel = 0, because only opcodes should be tagged as they are ?ead?from memory. rwaen and rwben are ignored when trgsel = 1. in full modes ( a and b?and a and not b? rwaen and rwa are used to select read or write comparisons for both comparators a and b. table 16-24 shows the effect for rwaen, rwa, and rw on the dbgcb comparison conditions. the rwben and rwb bits are not used and are ignored in full modes. 16.4.2.1.2 trigger selection the trgsel bit in dbgc1 is used to determine the triggering condition in dbg mode. trgsel applies to both trigger a and b except in the event only trigger modes. by setting trgsel, the comparators a and b will qualify a match with the output of opcode tracking logic and a trigger occurs before the tagged instruction executes (tagged-type trigger). with the trgsel bit cleared, a comparator match forces a trigger when the matching condition occurs (force-type trigger). note if the trgsel is set, the address stored in the comparator match address registers must be an opcode address for the trigger to occur. 16.4.2.2 trace buffer control (tbc) the tbc is the main controller for the dbg module. its function is to decide whether data should be stored in the trace buffer based on the trigger mode and the match signals from the comparator. the tbc also determines whether a request to break the cpu should occur. table 16-24. read or write comparison logic table rwaen bit rwa bit rw signal comment 0 x 0 write data bus 0 x 1 read data bus 1 0 0 write data bus 1 0 1 no data bus compare since rw=1 1 1 0 no data bus compare since rw=0 1 1 1 read data bus chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 495 16.4.2.3 begin- and end-trigger the de?itions of begin- and end-trigger as used in the dbg module are as follows: begin-trigger: storage in trace buffer occurs after the trigger and continues until 64 locations are ?led. end-trigger: storage in trace buffer occurs until the trigger, with the least recent data falling out of the trace buffer if more than 64 words are collected. 16.4.2.4 arming the dbg module in dbg mode, arming occurs by setting dbgen and arm in dbgc1. the arm bit in dbgc1 is cleared when the trigger condition is met in end-trigger mode or when the trace buffer is ?led in begin-trigger mode. the tbc logic determines whether a trigger condition has been met based on the trigger mode and the trigger selection. 16.4.2.5 trigger modes the dbg module supports nine trigger modes. the trigger modes are encoded as shown in table 16-6 . the trigger mode is used as a quali?r for either starting or ending the storing of data in the trace buffer. when the match condition is met, the appropriate ?g a or b is set in dbgsc. arming the dbg module clears the a, b, and c ?gs in dbgsc. in all trigger modes except for the event-only modes and detail capture mode, change-of-?w addresses are stored in the trace buffer. in the event-only modes only the value on the data bus at the trigger event b will be stored. in detail capture mode address and data for all cycles except program fetch (p) and free (f) cycles are stored in trace buffer. 16.4.2.5.1 a only in the a only trigger mode, if the match condition for a is met, the a ?g in dbgsc is set and a trigger occurs. 16.4.2.5.2 a or b in the a or b trigger mode, if the match condition for a or b is met, the corresponding ?g in dbgsc is set and a trigger occurs. 16.4.2.5.3 a then b in the a then b trigger mode, the match condition for a must be met before the match condition for b is compared. when the match condition for a or b is met, the corresponding ?g in dbgsc is set. the trigger occurs only after a then b have matched. note when tagging and using a then b, if addresses a and b are close together, then b may not complete the trigger sequence. this occurs when a and b are in the instruction queue at the same time. basically the a trigger has not yet occurred, so the b instruction is not tagged. generally, if address b is at chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 496 freescale semiconductor least six addresses higher than address a (or b is lower than a) and there are not changes of ?w to put these in the queue at the same time, then this operation should trigger properly. 16.4.2.5.4 event-only b (store data) in the event-only b trigger mode, if the match condition for b is met, the b ?g in dbgsc is set and a trigger occurs. the event-only b trigger mode is considered a begin-trigger type and the begin bit in dbgc1 is ignored. event-only b is incompatible with instruction tagging (trgsel = 1), and thus the value of trgsel is ignored. please refer to section 16.4.2.7, ?torage memory , for more information. this trigger mode is incompatible with the detail capture mode so the detail capture mode will have priority. trgsel and begin will not be ignored and this trigger mode will behave as if it were ? only? 16.4.2.5.5 a then event-only b (store data) in the a then event-only b trigger mode, the match condition for a must be met before the match condition for b is compared, after the a match has occurred, a trigger occurs each time b matches. when the match condition for a or b is met, the corresponding ?g in dbgsc is set. the a then event-only b trigger mode is considered a begin-trigger type and begin in dbgc1 is ignored. trgsel in dbgc1 applies only to the match condition for a. please refer to section 16.4.2.7, ?torage memory , for more information. this trigger mode is incompatible with the detail capture mode so the detail capture mode will have priority. trgsel and begin will not be ignored and this trigger mode will be the same as a then b. 16.4.2.5.6 a and b (full mode) in the a and b trigger mode, comparator a compares to the address bus and comparator b compares to the data bus. in the a and b trigger mode, if the match condition for a and b happen on the same bus cycle, both the a and b ?gs in the dbgsc register are set and a trigger occurs. if trgsel = 1, only matches from comparator a are used to determine if the trigger condition is met and comparator b matches are ignored. if trgsel = 0, full-word data matches on an odd address boundary (misaligned access) do not work unless the access is to a ram that manages misaligned accesses in a single clock cycle (which is typical of ram modules used in hcs12 mcus). 16.4.2.5.7 a and not b (full mode) in the a and not b trigger mode, comparator a compares to the address bus and comparator b compares to the data bus. in the a and not b trigger mode, if the match condition for a and not b happen on the same bus cycle, both the a and b ?gs in dbgsc are set and a trigger occurs. if trgsel = 1, only matches from comparator a are used to determine if the trigger condition is met and comparator b matches are ignored. as described in section 16.4.2.5.6, a and b (full mode) , full-word data compares on misaligned accesses will not match expected data (and thus will cause a trigger in this mode) unless the access is to a ram that manages misaligned accesses in a single clock cycle. chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 497 16.4.2.5.8 inside range (a address b) in the inside range trigger mode, if the match condition for a and b happen on the same bus cycle, both the a and b ?gs in dbgsc are set and a trigger occurs. if a match condition on only a or only b occurs no ?gs are set. if trgsel = 1, the inside range is accurate only to word boundaries. if trgsel = 0, an aligned word access which straddles the range boundary will cause a trigger only if the aligned address is within the range. 16.4.2.5.9 outside range (address < a or address > b) in the outside range trigger mode, if the match condition for a or b is met, the corresponding ?g in dbgsc is set and a trigger occurs. if trgsel = 1, the outside range is accurate only to word boundaries. if trgsel = 0, an aligned word access which straddles the range boundary will cause a trigger only if the aligned address is outside the range. 16.4.2.5.10 control bit priorities the de?itions of some of the control bits are incompatible with each other. table 16-25 and the notes associated with it summarize how these incompatibilities are managed: read/write comparisons are not compatible with trgsel = 1. therefore, rwaen and rwben are ignored. event-only trigger modes are always considered a begin-type trigger. see section 16.4.2.8.1, ?toring with begin-trigger , and section 16.4.2.8.2, ?toring with end-trigger . detail capture mode has priority over the event-only trigger/capture modes. therefore, event-only modes have no meaning in detail mode and their functions default to similar trigger modes. table 16-25. resolution of mode con?cts mode normal / loop1 detail tag force tag force a only a or b a then b event-only b 1 1, 3 3 a then event-only b 2 4 4 a and b (full mode) 5 5 a and not b (full mode) 5 5 inside range 6 6 outside range 6 6 1 ?ignored ?same as force 2 ?ignored for comparator b 3 ?reduces to effectively ? only 4 ?works same as a then b 5 ?reduces to effectively ? only??b not compared 6 ?only accurate to word boundaries chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 498 freescale semiconductor 16.4.2.6 capture modes the dbg in dbg mode can operate in four capture modes. these modes are described in the following subsections. 16.4.2.6.1 normal mode in normal mode, the dbg module uses comparator a and b as triggering devices. change-of-?w information or data will be stored depending on trg in dbgsc. 16.4.2.6.2 loop1 mode the intent of loop1 mode is to prevent the trace buffer from being ?led entirely with duplicate information from a looping construct such as delays using the dbne instruction or polling loops using brset/brclr instructions. immediately after address information is placed in the trace buffer, the dbg module writes this value into the c comparator and the c comparator is placed in ignore address mode. this will prevent duplicate address entries in the trace buffer resulting from repeated bit-conditional branches. comparator c will be cleared when the arm bit is set in loop1 mode to prevent the previous contents of the register from interfering with loop1 mode operation. breakpoints based on comparator c are disabled. loop1 mode only inhibits duplicate source address entries that would typically be stored in most tight looping constructs. it will not inhibit repeated entries of destination addresses or vector addresses, because repeated entries of these would most likely indicate a bug in the user s code that the dbg module is designed to help ?d. note in certain very tight loops, the source address will have already been fetched again before the c comparator is updated. this results in the source address being stored twice before further duplicate entries are suppressed. this condition occurs with branch-on-bit instructions when the branch is fetched by the ?st p-cycle of the branch or with loop-construct instructions in which the branch is fetched with the ?st or second p cycle. see examples below: loop incx ; 1-byte instruction fetched by 1st p-cycle of brclr brclr cmptmp,#$0c,loop ; the brclr instruction also will be fetched by 1st p-cycle of brclr loop2 brn * ; 2-byte instruction fetched by 1st p-cycle of dbne nop ; 1-byte instruction fetched by 2nd p-cycle of dbne dbne a,loop2 ; this instruction also fetched by 2nd p-cycle of dbne note loop1 mode does not support paged memory, and inhibits duplicate entries in the trace buffer based solely on the cpu address. there is a remote possibility of an erroneous address match if program ?w alternates between paged and unpaged memory space. chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 499 16.4.2.6.3 detail mode in the detail mode, address and data for all cycles except program fetch (p) and free (f) cycles are stored in trace buffer. this mode is intended to supply additional information on indexed, indirect addressing modes where storing only the destination address would not provide all information required for a user to determine where his code was in error. 16.4.2.6.4 pro?e mode this mode is intended to allow a host computer to poll a running target and provide a histogram of program execution. each read of the trace buffer address will return the address of the last instruction executed. the dbgcnt register is not incremented and the trace buffer does not get ?led. the arm bit is not used and all breakpoints and all other debug functions will be disabled. 16.4.2.7 storage memory the storage memory is a 64 words deep by 16-bits wide dual port ram array. the cpu accesses the ram array through a single memory location window (dbgtbh:dbgtbl). the dbg module stores trace information in the ram array in a circular buffer format. as data is read via the cpu, a pointer into the ram will increment so that the next cpu read will receive fresh information. in all trigger modes except for event-only and detail capture mode, the data stored in the trace buffer will be change-of-?w addresses. change-of-?w addresses are de?ed as follows: source address of conditional branches (long, short, brset, and loop constructs) taken destination address of indexed jmp, jsr, and call instruction destination address of rti, rts, and rtc instructions vector address of interrupts except for swi and bdm vectors in the event-only trigger modes only the 16-bit data bus value corresponding to the event is stored. in the detail capture mode, address and then data are stored for all cycles except program fetch (p) and free (f) cycles. 16.4.2.8 storing data in memory storage buffer 16.4.2.8.1 storing with begin-trigger storing with begin-trigger can be used in all trigger modes. when dbg mode is enabled and armed in the begin-trigger mode, data is not stored in the trace buffer until the trigger condition is met. as soon as the trigger condition is met, the dbg module will remain armed until 64 words are stored in the trace buffer. if the trigger is at the address of the change-of-?w instruction the change-of-?w associated with the trigger event will be stored in the trace buffer. 16.4.2.8.2 storing with end-trigger storing with end-trigger cannot be used in event-only trigger modes. when dbg mode is enabled and armed in the end-trigger mode, data is stored in the trace buffer until the trigger condition is met. when the trigger condition is met, the dbg module will become de-armed and no more data will be stored. if chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 500 freescale semiconductor the trigger is at the address of a change-of-?w address the trigger event will not be stored in the trace buffer. 16.4.2.9 reading data from trace buffer the data stored in the trace buffer can be read using either the background debug module (bdm) module or the cpu provided the dbg module is enabled and not armed. the trace buffer data is read out ?st-in ?st-out. by reading cnt in dbgcnt the number of valid words can be determined. cnt will not decrement as data is read from dbgtbh:dbgtbl. the trace buffer data is read by reading dbgtbh:dbgtbl with a 16-bit read. each time dbgtbh:dbgtbl is read, a pointer in the dbg will be incremented to allow reading of the next word. reading the trace buffer while the dbg module is armed will return invalid data and no shifting of the ram pointer will occur. note the trace buffer should be read with the dbg module enabled and in the same capture mode that the data was recorded. the contents of the trace buffer counter register (dbgcnt) are resolved differently in detail mode verses the other modes and may lead to incorrect interpretation of the trace buffer data. 16.4.3 breakpoints there are two ways of getting a breakpoint in dbg mode. one is based on the trigger condition of the trigger mode using comparator a and/or b, and the other is using comparator c. external breakpoints generated using the t a ghi and t a glo external pins are disabled in dbg mode. 16.4.3.1 breakpoint based on comparator a and b a breakpoint request to the cpu can be enabled by setting dbgbrk in dbgc1. the value of begin in dbgc1 determines when the breakpoint request to the cpu will occur. when begin in dbgc1 is set, begin-trigger is selected and the breakpoint request will not occur until the trace buffer is ?led with 64 words. when begin in dbgc1 is cleared, end-trigger is selected and the breakpoint request will occur immediately at the trigger cycle. there are two types of breakpoint requests supported by the dbg module, tagged and forced. tagged breakpoints are associated with opcode addresses and allow breaking just before a speci? instruction executes. forced breakpoints are not associated with opcode addresses and allow breaking at the next instruction boundary. the type of breakpoint based on comparators a and b is determined by trgsel in the dbgc1 register (trgsel = 1 for tagged breakpoint, trgsel = 0 for forced breakpoint). table 16-26 illustrates the type of breakpoint that will occur based on the debug run. chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 501 16.4.3.2 breakpoint based on comparator c a breakpoint request to the cpu can be created if bkcen in dbgc2 is set. breakpoints based on a successful comparator c match can be accomplished regardless of the mode of operation for comparator a or b, and do not affect the status of the arm bit. tagc in dbgc2 is used to select either tagged or forced breakpoint requests for comparator c. breakpoints based on comparator c are disabled in loop1 mode. note because breakpoints cannot be disabled when the dbg is armed, one must be careful to avoid an ?n?ite breakpoint loop when using tagged-type c breakpoints while the dbg is armed. if bdm breakpoints are selected, executing a trace1 instruction before the go instruction is the recommended way to avoid re-triggering a breakpoint if one does not wish to de-arm the dbg. if swi breakpoints are selected, disarming the dbg in the swi interrupt service routine is the recommended way to avoid re-triggering a breakpoint. 16.5 resets the dbg module is disabled after reset. the dbg module cannot cause a mcu reset. 16.6 interrupts the dbg contains one interrupt source. if a breakpoint is requested and bdm in dbgc2 is cleared, an swi interrupt will be generated. table 16-26. breakpoint setup begin trgsel dbgbrk type of debug run 0 0 0 fill trace buffer until trigger address (no cpu breakpoint ?keep running) 0 0 1 fill trace buffer until trigger address, then a forced breakpoint request occurs 0 1 0 fill trace buffer until trigger opcode is about to execute (no cpu breakpoint ?keep running) 0 1 1 fill trace buffer until trigger opcode about to execute, then a tagged breakpoint request occurs 1 0 0 start trace buffer at trigger address (no cpu breakpoint ?keep running) 1 0 1 start trace buffer at trigger address, a forced breakpoint request occurs when trace buffer is full 1 1 0 start trace buffer at trigger opcode (no cpu breakpoint ?keep running) 1 1 1 start trace buffer at trigger opcode, a forced breakpoint request occurs when trace buffer is full chapter 16 debug module (dbgv1) mc9s12kg128 data sheet, rev. 1.15 502 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 503 chapter 17 interrupt (intv1) 17.1 introduction this section describes the functionality of the interrupt (int) sub-block of the s12 core platform. a block diagram of the interrupt sub-block is shown in figure 17-1 . figure 17-1. int block diagram hprio (optional) int priority decoder vector request interrupts reset flags write data bus hprio vector xmask imask qualified interrupt input registers interrupts and control registers highest priority i-interrupt read data bus wakeup vector address interrupt pending chapter 17 interrupt (intv1) mc9s12kg128 data sheet, rev. 1.15 504 freescale semiconductor the interrupt sub-block decodes the priority of all system exception requests and provides the applicable vector for processing the exception. the int supports i-bit maskable and x-bit maskable interrupts, a non-maskable unimplemented opcode trap, a non-maskable software interrupt (swi) or background debug mode request, and three system reset vector requests. all interrupt related exception requests are managed by the interrupt sub-block (int). 17.1.1 features the int includes these features: provides two to 122 i-bit maskable interrupt vectors (0xff00?xfff2) provides one x-bit maskable interrupt vector (0xfff4) provides a non-maskable software interrupt (swi) or background debug mode request vector (0xfff6) provides a non-maskable unimplemented opcode trap (trap) vector (0xfff8) provides three system reset vectors (0xfffa?xfffe) (reset, cmr, and cop) determines the appropriate vector and drives it onto the address bus at the appropriate time signals the cpu that interrupts are pending provides control registers which allow testing of interrupts provides additional input signals which prevents requests for servicing i and x interrupts wakes the system from stop or wait mode when an appropriate interrupt occurs or whenever xirq is active, even if xirq is masked provides asynchronous path for all i and x interrupts, (0xff00?xfff4) (optional) selects and stores the highest priority i interrupt based on the value written into the hprio register 17.1.2 modes of operation the functionality of the int sub-block in various modes of operation is discussed in the subsections that follow. normal operation the int operates the same in all normal modes of operation. special operation interrupts may be tested in special modes through the use of the interrupt test registers. emulation modes the int operates the same in emulation modes as in normal modes. low power modes see section 17.4.1, ?ow-power modes , for details chapter 17 interrupt (intv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 505 17.2 external signal description most interfacing with the interrupt sub-block is done within the core. however, the interrupt does receive direct input from the multiplexed external bus interface (mebi) sub-block of the core for the irq and xirq pin data. 17.3 memory map and register de?ition detailed descriptions of the registers and associated bits are given in the subsections that follow. 17.3.1 module memory map 17.3.2 register descriptions 17.3.2.1 interrupt test control register read: see individual bit descriptions write: see individual bit descriptions table 17-1. int memory map address offset use access 0x0015 interrupt test control register (itcr) r/w 0x0016 interrupt test registers (itest) r/w 0x001f highest priority interrupt (optional) (hprio) r/w 76543210 r000 wrtint adr3 adr2 adr1 adr0 w reset 0 0 0 01111 = unimplemented or reserved figure 17-2. interrupt test control register (itcr) chapter 17 interrupt (intv1) mc9s12kg128 data sheet, rev. 1.15 506 freescale semiconductor 17.3.2.2 interrupt test registers read: only in special modes. reads will return either the state of the interrupt inputs of the interrupt sub-block (wrtint = 0) or the values written into the test registers (wrtint = 1). reads will always return 0s in normal modes. write: only in special modes and with wrtint = 1 and ccr i mask = 1. table 17-2. itcr field descriptions field description 4 wrtint write to the interrupt test registers read: anytime write: only in special modes and with i-bit mask and x-bit mask set. 0 disables writes to the test registers; reads of the test registers will return the state of the interrupt inputs. 1 disconnect the interrupt inputs from the priority decoder and use the values written into the itest registers instead. note: any interrupts which are pending at the time that wrtint is set will remain until they are overwritten. 3:0 adr[3:0] test register select bits read: anytime write: anytime these bits determine which test register is selected on a read or write. the hexadecimal value written here will be the same as the upper nibble of the lower byte of the vector selects. that is, an ? written into adr[3:0] will select vectors 0xfffe?xfff0 while a ??written to adr[3:0] will select vectors 0xff7e?xff70. 76543210 r inte intc inta int8 int6 int4 int2 int0 w reset 0 0 0 00000 = unimplemented or reserved figure 17-3. interrupt test registers (itest) table 17-3. itest field descriptions field description 7:0 int[e:0] interrupt test bits ?these registers are used in special modes for testing the interrupt logic and priority independent of the system con?uration. each bit is used to force a speci? interrupt vector by writing it to a logic 1 state. bits are named inte through int0 to indicate vectors 0xffxe through 0xffx0. these bits can be written only in special modes and only with the wrtint bit set (logic 1) in the interrupt test control register (itcr). in addition, i interrupts must be masked using the i bit in the ccr. in this state, the interrupt input lines to the interrupt sub-block will be disconnected and interrupt requests will be generated only by this register. these bits can also be read in special modes to view that an interrupt requested by a system block (such as a peripheral block) has reached the int module. there is a test register implemented for every eight interrupts in the overall system. all of the test registers share the same address and are individually selected using the value stored in the adr[3:0] bits of the interrupt test control register (itcr). note: when adr[3:0] have the value of 0x000f, only bits 2:0 in the itest register will be accessible. that is, vectors higher than 0xfff4 cannot be tested using the test registers and bits 7:3 will always read as a logic 0. if adr[3:0] point to an unimplemented test register, writes will have no effect and reads will always return a logic 0 value. chapter 17 interrupt (intv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 507 17.3.2.3 highest priority i interrupt (optional) read: anytime write: only if i mask in ccr = 1 17.4 functional description the interrupt sub-block processes all exception requests made by the cpu. these exceptions include interrupt vector requests and reset vector requests. each of these exception types and their overall priority level is discussed in the subsections below. 17.4.1 low-power modes the int does not contain any user-controlled options for reducing power consumption. the operation of the int in low-power modes is discussed in the following subsections. 17.4.1.1 operation in run mode the int does not contain any options for reducing power in run mode. 17.4.1.2 operation in wait mode clocks to the int can be shut off during system wait mode and the asynchronous interrupt path will be used to generate the wake-up signal upon recognition of a valid interrupt or any xirq request. 17.4.1.3 operation in stop mode clocks to the int can be shut off during system stop mode and the asynchronous interrupt path will be used to generate the wake-up signal upon recognition of a valid interrupt or any xirq request. 76543210 r psel7 psel6 psel5 psel4 psel3 psel2 psel1 0 w reset 1 1 1 10010 = unimplemented or reserved figure 17-4. highest priority i interrupt register (hprio) table 17-4. hprio field descriptions field description 7:1 psel[7:1] highest priority i interrupt select bits the state of these bits determines which i-bit maskable interrupt will be promoted to highest priority (of the i-bit maskable interrupts). to promote an interrupt, the user writes the least signi?ant byte of the associated interrupt vector address to this register. if an unimplemented vector address or a non i-bit masked vector address (value higher than 0x00f2) is written, irq (0xfff2) will be the default highest priority interrupt. chapter 17 interrupt (intv1) mc9s12kg128 data sheet, rev. 1.15 508 freescale semiconductor 17.5 resets the int supports three system reset exception request types: normal system reset or power-on-reset request, crystal monitor reset request, and cop watchdog reset request. the type of reset exception request must be decoded by the system and the proper request made to the core. the int will then provide the service routine address for the type of reset requested. 17.6 interrupts as shown in the block diagram in figure 17-1 , the int contains a register block to provide interrupt status and control, an optional highest priority i interrupt (hprio) block, and a priority decoder to evaluate whether pending interrupts are valid and assess their priority. 17.6.1 interrupt registers the int registers are accessible only in special modes of operation and function as described in section 17.3.2.1, ?nterrupt test control register , and section 17.3.2.2, ?nterrupt test registers , previously. 17.6.2 highest priority i-bit maskable interrupt when the optional hprio block is implemented, the user is allowed to promote a single i-bit maskable interrupt to be the highest priority i interrupt. the hprio evaluates all interrupt exception requests and passes the hprio vector to the priority decoder if the highest priority i interrupt is active. rti replaces the promoted interrupt source. 17.6.3 interrupt priority decoder the priority decoder evaluates all interrupts pending and determines their validity and priority. when the cpu requests an interrupt vector, the decoder will provide the vector for the highest priority interrupt request. because the vector is not supplied until the cpu requests it, it is possible that a higher priority interrupt request could override the original exception that caused the cpu to request the vector. in this case, the cpu will receive the highest priority vector and the system will process this exception instead of the original request. note care must be taken to ensure that all exception requests remain active until the system begins execution of the applicable service routine; otherwise, the exception request may not be processed. if for any reason the interrupt source is unknown (e.g., an interrupt request becomes inactive after the interrupt has been recognized but prior to the vector request), the vector address will default to that of the last valid interrupt that existed during the particular interrupt sequence. if the cpu requests an interrupt vector when there has never been a pending interrupt request, the int will provide the software interrupt (swi) vector address. chapter 17 interrupt (intv1) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 509 17.7 exception priority the priority (from highest to lowest) and address of all exception vectors issued by the int upon request by the cpu is shown in table 17-5 . table 17-5. exception vector map and priority vector address source 0xfffe?xffff system reset 0xfffc?xfffd crystal monitor reset 0xfffa?xfffb cop reset 0xfff8?xfff9 unimplemented opcode trap 0xfff6?xfff7 software interrupt instruction (swi) or bdm vector request 0xfff4?xfff5 xirq signal 0xfff2?xfff3 irq signal 0xfff0?xff00 device-speci? i-bit maskable interrupt sources (priority in descending order) chapter 17 interrupt (intv1) mc9s12kg128 data sheet, rev. 1.15 510 freescale semiconductor mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 511 chapter 18 multiplexed external bus interface (mebiv3) 18.1 introduction this section describes the functionality of the multiplexed external bus interface (mebi) sub-block of the s12 core platform. the functionality of the module is closely coupled with the s12 cpu and the memory map controller (mmc) sub-blocks. figure 18-1 is a block diagram of the mebi. in figure 18-1 , the signals on the right hand side represent pins that are accessible externally. on some chips, these may not all be bonded out. the mebi sub-block of the core serves to provide access and/or visibility to internal core data manipulation operations including timing reference information at the external boundary of the core and/or system. depending upon the system operating mode and the state of bits within the control registers of the mebi, the internal 16-bit read and write data operations will be represented in 8-bit or 16-bit accesses externally. using control information from other blocks within the system, the mebi will determine the appropriate type of data access to be generated. 18.1.1 features the block name includes these distinctive features: external bus controller with four 8-bit ports a,b, e, and k data and data direction registers for ports a, b, e, and k when used as general-purpose i/o control register to enable/disable alternate functions on ports e and k mode control register control register to enable/disable pull resistors on ports a, b, e, and k control register to enable/disable reduced output drive on ports a, b, e, and k control register to con?ure external clock behavior control register to con?ure irq pin operation logic to capture and synchronize external interrupt pin inputs chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 512 freescale semiconductor figure 18-1. mebi block diagram pe[7:2]/noacc/ pe1/ irq pe0/ xirq bkgd/modc/ t a ghi pk[7:0]/ ecs/ xcs/x[19:14] pa[7:0]/a[15:8]/ d[15:8]/d[7:0] port k port a pb[7:0]/a[7:0]/ d[7:0] port b port e bkgd regs ext bus i/f ctl addr[19:0] data[15:0] (control) internal bus eclk ctl irq ctl addr addr data addr data pipe ctl cpu pipe info irq interrupt xirq interrupt bdm tag info ipipe1/modb/clkto ipipe0/moda/ eclk/ lstrb/ t a glo r/ w tag ctl control signal(s) data signal (unidirectional) data bus (unidirectional) data bus (bidirectional) data signal (bidirectional) mode chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 513 18.1.2 modes of operation normal expanded wide mode ports a and b are con?ured as a 16-bit multiplexed address and data bus and port e provides bus control and status signals. this mode allows 16-bit external memory and peripheral devices to be interfaced to the system. normal expanded narrow mode ports a and b are con?ured as a 16-bit address bus and port a is multiplexed with 8-bit data. port e provides bus control and status signals. this mode allows 8-bit external memory and peripheral devices to be interfaced to the system. normal single-chip mode there is no external expansion bus in this mode. the processor program is executed from internal memory. ports a, b, k, and most of e are available as general-purpose i/o. special single-chip mode this mode is generally used for debugging single-chip operation, boot-strapping, or security related operations. the active background mode is in control of cpu execution and bdm ?mware is waiting for additional serial commands through the bkgd pin. there is no external expansion bus after reset in this mode. emulation expanded wide mode developers use this mode for emulation systems in which the users target application is normal expanded wide mode. emulation expanded narrow mode developers use this mode for emulation systems in which the users target application is normal expanded narrow mode. special test mode ports a and b are con?ured as a 16-bit multiplexed address and data bus and port e provides bus control and status signals. in special test mode, the write protection of many control bits is lifted so that they can be thoroughly tested without needing to go through reset. special peripheral mode this mode is intended for freescale semiconductor factory testing of the system. the cpu is inactive and an external (tester) bus master drives address, data, and bus control signals. 18.2 external signal description in typical implementations, the mebi sub-block of the core interfaces directly with external system pins. some pins may not be bonded out in all implementations. table 18-1 outlines the pin names and functions and gives a brief description of their operation reset state of these pins and associated pull-ups or pull-downs is dependent on the mode of operation and on the integration of this block at the chip level (chip dependent). chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 514 freescale semiconductor . table 18-1. external system pins associated with mebi pin name pin functions description bkgd/modc/ t a ghi modc at the rising edge on reset, the state of this pin is registered into the modc bit to set the mode. (this pin always has an internal pullup.) bkgd pseudo open-drain communication pin for the single-wire background debug mode. there is an internal pull-up resistor on this pin. t a ghi when instruction tagging is on, a 0 at the falling edge of e tags the high half of the instruction word being read into the instruction queue. pa7/a15/d15/d7 thru pa0/a8/d8/d0 pa7?a0 general-purpose i/o pins, see porta and ddra registers. a15?8 high-order address lines multiplexed during eclk low. outputs except in special peripheral mode where they are inputs from an external tester system. d15?8 high-order bidirectional data lines multiplexed during eclk high in expanded wide modes, special peripheral mode, and visible internal accesses (ivis = 1) in emulation expanded narrow mode. direction of data transfer is generally indicated by r/ w. d15/d7 thru d8/d0 alternate high-order and low-order bytes of the bidirectional data lines multiplexed during eclk high in expanded narrow modes and narrow accesses in wide modes. direction of data transfer is generally indicated by r/ w. pb7/a7/d7 thru pb0/a0/d0 pb7?b0 general-purpose i/o pins, see portb and ddrb registers. a7?0 low-order address lines multiplexed during eclk low. outputs except in special peripheral mode where they are inputs from an external tester system. d7?0 low-order bidirectional data lines multiplexed during eclk high in expanded wide modes, special peripheral mode, and visible internal accesses (with ivis = 1) in emulation expanded narrow mode. direction of data transfer is generally indicated by r/ w. pe7/noacc pe7 general-purpose i/o pin, see porte and ddre registers. noacc cpu no access output. indicates whether the current cycle is a free cycle. only available in expanded modes. pe6/ipipe1/ modb/clkto modb at the rising edge of reset, the state of this pin is registered into the modb bit to set the mode. pe6 general-purpose i/o pin, see porte and ddre registers. ipipe1 instruction pipe status bit 1, enabled by pipoe bit in pear. clkto system clock test output. only available in special modes. pipoe = 1 overrides this function. the enable for this function is in the clock module. pe5/ipipe0/moda moda at the rising edge on reset, the state of this pin is registered into the moda bit to set the mode. pe5 general-purpose i/o pin, see porte and ddre registers. ipipe0 instruction pipe status bit 0, enabled by pipoe bit in pear. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 515 detailed descriptions of these pins can be found in the device overview chapter. 18.3 memory map and register de?ition a summary of the registers associated with the mebi sub-block is shown in table 18-2 . detailed descriptions of the registers and bits are given in the subsections that follow. on most chips the registers are mappable. therefore, the upper bits may not be all 0s as shown in the table and descriptions. pe4/eclk pe4 general-purpose i/o pin, see porte and ddre registers. eclk bus timing reference clock, can operate as a free-running clock at the system clock rate or to produce one low-high clock per visible access, with the high period stretched for slow accesses. eclk is controlled by the neclk bit in pear, the ivis bit in mode, and the estr bit in ebictl. pe3/ lstrb/ t a glo pe3 general-purpose i/o pin, see porte and ddre registers. lstrb low strobe bar, 0 indicates valid data on d7?0. sz8 in special peripheral mode, this pin is an input indicating the size of the data transfer (0 = 16-bit; 1 = 8-bit). t a glo in expanded wide mode or emulation narrow modes, when instruction tagging is on and low strobe is enabled, a 0 at the falling edge of e tags the low half of the instruction word being read into the instruction queue. pe2/r/ w pe2 general-purpose i/o pin, see porte and ddre registers. r/ w read/write, indicates the direction of internal data transfers. this is an output except in special peripheral mode where it is an input. pe1/ irq pe1 general-purpose input-only pin, can be read even if irq enabled. irq maskable interrupt request, can be level sensitive or edge sensitive. pe0/ xirq pe0 general-purpose input-only pin. xirq non-maskable interrupt input. pk7/ ecs pk7 general-purpose i/o pin, see portk and ddrk registers. ecs emulation chip select pk6/ xcs pk6 general-purpose i/o pin, see portk and ddrk registers. xcs external data chip select pk5/x19 thru pk0/x14 pk5?k0 general-purpose i/o pins, see portk and ddrk registers. x19?14 memory expansion addresses table 18-1. external system pins associated with mebi (continued) pin name pin functions description chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 516 freescale semiconductor 18.3.1 module memory map 18.3.2 register descriptions 18.3.2.1 port a data register (porta) table 18-2. mebi memory map address offset use access 0x0000 port a data register (porta) r/w 0x0001 port b data register (portb) r/w 0x0002 data direction register a (ddra) r/w 0x0003 data direction register b (ddrb) r/w 0x0004 reserved r 0x0005 reserved r 0x0006 reserved r 0x0007 reserved r 0x0008 port e data register (porte) r/w 0x0009 data direction register e (ddre) r/w 0x000a port e assignment register (pear) r/w 0x000b mode register (mode) r/w 0x000c pull control register (pucr) r/w 0x000d reduced drive register (rdriv) r/w 0x000e external bus interface control register (ebictl) r/w 0x000f reserved r 0x001e irq control register (irqcr) r/w 0x00032 port k data register (portk) r/w 0x00033 data direction register k (ddrk) r/w 76543210 r bit 7 6 5 4 3 2 1 bit 0 w reset 0 0 0 0 0 0 0 0 single chip pa7 pa6 pa5 pa4 pa3 pa2 pa1 pa0 expanded wide, emulation narrow with ivis, and peripheral ab/db15 ab/db14 ab/db13 ab/db12 ab/db11 ab/db10 ab/db9 ab/db8 expanded narrow ab15 and db15/db7 ab14 and db14/db6 ab13 and db13/db5 ab12 and db12/db4 ab11 and db11/db3 ab10 and db10/db2 ab9 and db9/db1 ab8 and db8/db0 figure 18-2. port a data register (porta) chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 517 read: anytime when register is in the map write: anytime when register is in the map port a bits 7 through 0 are associated with address lines a15 through a8 respectively and data lines d15/d7 through d8/d0 respectively. when this port is not used for external addresses such as in single-chip mode, these pins can be used as general-purpose i/o. data direction register a (ddra) determines the primary direction of each pin. ddra also determines the source of data for a read of porta. this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. note to ensure that you read the value present on the porta pins, always wait at least one cycle after writing to the ddra register before reading from the porta register. 18.3.2.2 port b data register (portb) read: anytime when register is in the map write: anytime when register is in the map port b bits 7 through 0 are associated with address lines a7 through a0 respectively and data lines d7 through d0 respectively. when this port is not used for external addresses, such as in single-chip mode, these pins can be used as general-purpose i/o. data direction register b (ddrb) determines the primary direction of each pin. ddrb also determines the source of data for a read of portb. this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. note to ensure that you read the value present on the portb pins, always wait at least one cycle after writing to the ddrb register before reading from the portb register. 76543210 r bit 7 6 5 4 3 2 1 bit 0 w reset 0 0 0 0 0 0 0 0 single chip pb7 pb6 pb5 pb4 pb3 pb2 pb1 pb0 expanded wide, emulation narrow with ivis, and peripheral ab/db7 ab/db6 ab/db5 ab/db4 ab/db3 ab/db2 ab/db1 ab/db0 expanded narrow ab7 ab6 ab5 ab4 ab3 ab2 ab1 ab0 figure 18-3. port a data register (portb) chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 518 freescale semiconductor 18.3.2.3 data direction register a (ddra) read: anytime when register is in the map write: anytime when register is in the map this register controls the data direction for port a. when port a is operating as a general-purpose i/o port, ddra determines the primary direction for each port a pin. a 1 causes the associated port pin to be an output and a 0 causes the associated pin to be a high-impedance input. the value in a ddr bit also affects the source of data for reads of the corresponding porta register. if the ddr bit is 0 (input) the buffered pin input state is read. if the ddr bit is 1 (output) the associated port data register bit state is read. this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. it is reset to 0x00 so the ddr does not override the three-state control signals. 76543210 r bit 7 6 5 4321 bit 0 w reset 0 0 0 00000 figure 18-4. data direction register a (ddra) table 18-3. ddra field descriptions field description 7:0 ddra data direction port a 0 con?ure the corresponding i/o pin as an input 1 con?ure the corresponding i/o pin as an output chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 519 18.3.2.4 data direction register b (ddrb) read: anytime when register is in the map write: anytime when register is in the map this register controls the data direction for port b. when port b is operating as a general-purpose i/o port, ddrb determines the primary direction for each port b pin. a 1 causes the associated port pin to be an output and a 0 causes the associated pin to be a high-impedance input. the value in a ddr bit also affects the source of data for reads of the corresponding portb register. if the ddr bit is 0 (input) the buffered pin input state is read. if the ddr bit is 1 (output) the associated port data register bit state is read. this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. it is reset to 0x00 so the ddr does not override the three-state control signals. 76543210 r bit 7 6 5 4321 bit 0 w reset 0 0 0 00000 figure 18-5. data direction register b (ddrb) table 18-4. ddrb field descriptions field description 7:0 ddrb data direction port b 0 con?ure the corresponding i/o pin as an input 1 con?ure the corresponding i/o pin as an output chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 520 freescale semiconductor 18.3.2.5 reserved registers these register locations are not used (reserved). all unused registers and bits in this block return logic 0s when read. writes to these registers have no effect. these registers are not in the on-chip map in special peripheral mode. 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 18-6. reserved register 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 18-7. reserved register 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 18-8. reserved register 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 18-9. reserved register chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 521 18.3.2.6 port e data register (porte) read: anytime when register is in the map write: anytime when register is in the map port e is associated with external bus control signals and interrupt inputs. these include mode select (modb/ipipe1, moda/ipipe0), e clock, size ( lstrb/ t a glo), read/write (r/ w), irq, and xirq. when not used for one of these speci? functions, port e pins 7:2 can be used as general-purpose i/o and pins 1:0 can be used as general-purpose input. the port e assignment register (pear) selects the function of each pin and ddre determines whether each pin is an input or output when it is con?ured to be general-purpose i/o. ddre also determines the source of data for a read of porte. some of these pins have software selectable pull resistors. irq and xirq can only be pulled up whereas the polarity of the pe7, pe4, pe3, and pe2 pull resistors are determined by chip integration. please refer to the device overview chapter (signal property summary) to determine the polarity of these resistors. a single control bit enables the pull devices for all of these pins when they are con?ured as inputs. this register is not in the on-chip map in special peripheral mode or in expanded modes when the eme bit is set. therefore, these accesses will be echoed externally. note it is unwise to write porte and ddre as a word access. if you are changing port e pins from being inputs to outputs, the data may have extra transitions during the write. it is best to initialize porte before enabling as outputs. note to ensure that you read the value present on the porte pins, always wait at least one cycle after writing to the ddre register before reading from the porte register. 76543210 r bit 7 65432 bit 1 bit 0 w reset 000000uu alternate pin function noacc modb or ipipe1 or clkto moda or ipipe0 eclk lstrb or t a glo r/ w irq xirq = unimplemented or reserved u = unaffected by reset figure 18-10. port e data register (porte) chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 522 freescale semiconductor 18.3.2.7 data direction register e (ddre) read: anytime when register is in the map write: anytime when register is in the map data direction register e is associated with port e. for bits in port e that are con?ured as general-purpose i/o lines, ddre determines the primary direction of each of these pins. a 1 causes the associated bit to be an output and a 0 causes the associated bit to be an input. port e bit 1 (associated with irq) and bit 0 (associated with xirq) cannot be con?ured as outputs. port e, bits 1 and 0, can be read regardless of whether the alternate interrupt function is enabled. the value in a ddr bit also affects the source of data for reads of the corresponding porte register. if the ddr bit is 0 (input) the buffered pin input state is read. if the ddr bit is 1 (output) the associated port data register bit state is read. this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. also, it is not in the map in expanded modes while the eme control bit is set. 76543210 r bit 7 6 5 4 3 bit 2 00 w reset 0 0 0 00000 = unimplemented or reserved figure 18-11. data direction register e (ddre) table 18-5. ddre field descriptions field description 7:2 ddre data direction port e 0 con?ure the corresponding i/o pin as an input 1 con?ure the corresponding i/o pin as an output note: it is unwise to write porte and ddre as a word access. if you are changing port e pins from inputs to outputs, the data may have extra transitions during the write. it is best to initialize porte before enabling as outputs. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 523 18.3.2.8 port e assignment register (pear) read: anytime (provided this register is in the map). write: each bit has speci? write conditions. please refer to the descriptions of each bit on the following pages. port e serves as general-purpose i/o or as system and bus control signals. the pear register is used to choose between the general-purpose i/o function and the alternate control functions. when an alternate control function is selected, the associated ddre bits are overridden. the reset condition of this register depends on the mode of operation because bus control signals are needed immediately after reset in some modes. in normal single-chip mode, no external bus control signals are needed so all of port e is con?ured for general-purpose i/o. in normal expanded modes, only the e clock is con?ured for its alternate bus control function and the other bits of port e are con?ured for general-purpose i/o. as the reset vector is located in external memory, the e clock is required for this access. r/ w is only needed by the system when there are external writable resources. if the normal expanded system needs any other bus control signals, pear would need to be written before any access that needed the additional signals. in special test and emulation modes, ipipe1, ipipe0, e, lstrb, and r/ w are con?ured out of reset as bus control signals. this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. 76543210 r noacce 0 pipoe neclk lstre rdwe 00 w reset special single chip 0 0 0 0 0 0 0 0 special test 0 0 1 0 1 1 0 0 peripheral 0 0 0 0 0 0 0 0 emulation expanded narrow 10101100 emulation expanded wide 10101100 normal single chip 0 0 0 1 0 0 0 0 normal expanded narrow 00000000 normal expanded wide 0 0 0 0 0 0 0 0 = unimplemented or reserved figure 18-12. port e assignment register (pear) chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 524 freescale semiconductor table 18-6. pear field descriptions field description 7 noacce cpu no access output enable normal: write once emulation: write never special: write anytime 1 the associated pin (port e, bit 7) is general-purpose i/o. 0 the associated pin (port e, bit 7) is output and indicates whether the cycle is a cpu free cycle. this bit has no effect in single-chip or special peripheral modes. 5 pipoe pipe status signal output enable normal: write once emulation: write never special: write anytime. 0 the associated pins (port e, bits 6:5) are general-purpose i/o. 1 the associated pins (port e, bits 6:5) are outputs and indicate the state of the instruction queue this bit has no effect in single-chip or special peripheral modes. 4 neclk no external e clock normal and special: write anytime emulation: write never 0 the associated pin (port e, bit 4) is the external e clock pin. external e clock is free-running if estr = 0 1 the associated pin (port e, bit 4) is a general-purpose i/o pin. external e clock is available as an output in all modes. 3 lstre low strobe ( lstrb) enable normal: write once emulation: write never special: write anytime. 0 the associated pin (port e, bit 3) is a general-purpose i/o pin. 1 the associated pin (port e, bit 3) is con?ured as the lstrb bus control output. if bdm tagging is enabled, t a glo is multiplexed in on the rising edge of eclk and lstrb is driven out on the falling edge of eclk. this bit has no effect in single-chip, peripheral, or normal expanded narrow modes. note: lstrb is used during external writes. after reset in normal expanded mode, lstrb is disabled to provide an extra i/o pin. if lstrb is needed, it should be enabled before any external writes. external reads do not normally need lstrb because all 16 data bits can be driven even if the system only needs 8 bits of data. 2 rdwe read/write enable normal: write once emulation: write never special: write anytime 0 the associated pin (port e, bit 2) is a general-purpose i/o pin. 1 the associated pin (port e, bit 2) is con?ured as the r/ w pin this bit has no effect in single-chip or special peripheral modes. note: r/ w is used for external writes. after reset in normal expanded mode, r/ w is disabled to provide an extra i/o pin. if r/ w is needed it should be enabled before any external writes. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 525 18.3.2.9 mode register (mode) read: anytime (provided this register is in the map). write: each bit has specific write conditions. please refer to the descriptions of each bit on the following pages. the mode register is used to establish the operating mode and other miscellaneous functions (i.e., internal visibility and emulation of port e and k). in special peripheral mode, this register is not accessible but it is reset as shown to system con?uration features. changes to bits in the mode register are delayed one cycle after the write. this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. 76543210 r modc modb moda 0 ivis 0 emk eme w reset special single chip 0 0 0 0 0 0 0 0 emulation expanded narrow 00101011 special test 0 1 0 0 1 0 0 0 emulation expanded wide 01101011 normal single chip 1 0 0 0 0 0 0 0 normal expanded narrow 10100000 peripheral 1 1 0 0 0 0 0 0 normal expanded wide 1 1 1 0 0 0 0 0 = unimplemented or reserved figure 18-13. mode register (mode) chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 526 freescale semiconductor table 18-7. mode field descriptions field description 7:5 mod[c:a] mode select bits ?these bits indicate the current operating mode. if moda = 1, then modc, modb, and moda are write never. if modc = moda = 0, then modc, modb, and moda are writable with the exception that you cannot change to or from special peripheral mode if modc = 1, modb = 0, and moda = 0, then modc is write never. modb and moda are write once, except that you cannot change to special peripheral mode. from normal single-chip, only normal expanded narrow and normal expanded wide modes are available. see table 18-8 and table 18-16 . 3 ivis internal visibility (for both read and write accesses) ?this bit determines whether internal accesses generate a bus cycle that is visible on the external bus. normal: write once emulation: write never special: write anytime 0 no visibility of internal bus operations on external bus. 1 internal bus operations are visible on external bus. 1 emk emulate port k normal: write once emulation: write never special: write anytime 0 portk and ddrk are in the memory map so port k can be used for general-purpose i/o. 1 if in any expanded mode, portk and ddrk are removed from the memory map. in single-chip modes, portk and ddrk are always in the map regardless of the state of this bit. in special peripheral mode, portk and ddrk are never in the map regardless of the state of this bit. 0 eme emulate port e normal and emulation: write never special: write anytime 0 porte and ddre are in the memory map so port e can be used for general-purpose i/o. 1 if in any expanded mode or special peripheral mode, porte and ddre are removed from the memory map. removing the registers from the map allows the user to emulate the function of these registers externally. in single-chip modes, porte and ddre are always in the map regardless of the state of this bit. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 527 18.3.2.10 pull control register (pucr) read: anytime (provided this register is in the map). write: anytime (provided this register is in the map). this register is used to select pull resistors for the pins associated with the core ports. pull resistors are assigned on a per-port basis and apply to any pin in the corresponding port that is currently con?ured as an input. the polarity of these pull resistors is determined by chip integration. please refer to the device overview chapter to determine the polarity of these resistors. table 18-8. modc, modb, and moda write capability 1 1 no writes to the mod bits are allowed while operating in a secure mode. for more details, refer to the device overview chapter. modc modb moda mode modx write capability 0 0 0 special single chip modc, modb, and moda write anytime but not to 110 2 2 if you are in a special single-chip or special test mode and you write to this register, changing to normal sin- gle-chip mode, then one allowed write to this register remains. if you write to normal expanded or emulation mode, then no writes remain. 0 0 1 emulation narrow no write 0 1 0 special test modc, modb, and moda write anytime but not to 110 (2) 0 1 1 emulation wide no write 1 0 0 normal single chip modc write never, modb and moda write once but not to 110 1 0 1 normal expanded narrow no write 1 1 0 special peripheral no write 1 1 1 normal expanded wide no write 76543210 r pupke 00 pupee 00 pupbe pupae w reset 1 10010000 notes: 1. the default value of this parameter is shown. please refer to the device overview chapter to deter- mine the actual reset state of this register. = unimplemented or reserved figure 18-14. pull control register (pucr) chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 528 freescale semiconductor this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. note these bits have no effect when the associated pin(s) are outputs. (the pull resistors are inactive.) 18.3.2.11 reduced drive register (rdriv) read: anytime (provided this register is in the map) write: anytime (provided this register is in the map) this register is used to select reduced drive for the pins associated with the core ports. this gives reduced power consumption and reduced rfi with a slight increase in transition time (depending on loading). this feature would be used on ports which have a light loading. the reduced drive function is independent of which function is being used on a particular port. this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. table 18-9. pucr field descriptions field description 7 pupke pull resistors port k enable 0 port k pull resistors are disabled. 1 enable pull resistors for port k input pins. 4 pupee pull resistors port e enable 0 port e pull resistors on bits 7, 4:0 are disabled. 1 enable pull resistors for port e input pins bits 7, 4:0. note: pins 5 and 6 of port e have pull resistors which are only enabled during reset. this bit has no effect on these pins. 1 pupbe pull resistors port b enable 0 port b pull resistors are disabled. 1 enable pull resistors for all port b input pins. 0 pupae pull resistors port a enable 0 port a pull resistors are disabled. 1 enable pull resistors for all port a input pins. 76543210 r rdrk 00 rdpe 00 rdpb rdpa w reset 00000000 = unimplemented or reserved figure 18-15. reduced drive register (rdriv) chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 529 18.3.2.12 external bus interface control register (ebictl) read: anytime (provided this register is in the map) write: refer to individual bit descriptions below the ebictl register is used to control miscellaneous functions (i.e., stretching of external e clock). this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. table 18-10. rdriv field descriptions field description 7 rdrk reduced drive of port k 0 all port k output pins have full drive enabled. 1 all port k output pins have reduced drive enabled. 4 rdpe reduced drive of port e 0 all port e output pins have full drive enabled. 1 all port e output pins have reduced drive enabled. 1 rdpb reduced drive of port b 0 all port b output pins have full drive enabled. 1 all port b output pins have reduced drive enabled. 0 rdpa reduced drive of ports a 0 all port a output pins have full drive enabled. 1 all port a output pins have reduced drive enabled. 76543210 r0000000 estr w reset: peripheral all other modes 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 = unimplemented or reserved figure 18-16. external bus interface control register (ebictl) table 18-11. ebictl field descriptions field description 0 estr e clock stretches this control bit determines whether the e clock behaves as a simple free-running clock or as a bus control signal that is active only for external bus cycles. normal and emulation: write once special: write anytime 0 e never stretches (always free running). 1 e stretches high during stretched external accesses and remains low during non-visible internal accesses. this bit has no effect in single-chip modes. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 530 freescale semiconductor 18.3.2.13 reserved register this register location is not used (reserved). all bits in this register return logic 0s when read. writes to this register have no effect. this register is not in the on-chip memory map in expanded and special peripheral modes. therefore, these accesses will be echoed externally. 18.3.2.14 irq control register (irqcr) read: see individual bit descriptions below write: see individual bit descriptions below 76543210 r00000000 w reset 00000000 = unimplemented or reserved figure 18-17. reserved register 76543210 r irqe irqen 000000 w reset 01000000 = unimplemented or reserved figure 18-18. irq control register (irqcr) table 18-12. irqcr field descriptions field description 7 irqe irq select edge sensitive only special modes: read or write anytime normal and emulation modes: read anytime, write once 0 irq con?ured for low level recognition. 1 irq con?ured to respond only to falling edges. falling edges on the irq pin will be detected anytime irqe = 1 and will be cleared only upon a reset or the servicing of the irq interrupt. 6 irqen external irq enable normal, emulation, and special modes: read or write anytime 0 external irq pin is disconnected from interrupt logic. 1 external irq pin is connected to interrupt logic. note: when irqen = 0, the edge detect latch is disabled. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 531 18.3.2.15 port k data register (portk) read: anytime write: anytime this port is associated with the internal memory expansion emulation pins. when the port is not enabled to emulate the internal memory expansion, the port pins are used as general-purpose i/o. when port k is operating as a general-purpose i/o port, ddrk determines the primary direction for each port k pin. a 1 causes the associated port pin to be an output and a 0 causes the associated pin to be a high-impedance input. the value in a ddr bit also affects the source of data for reads of the corresponding portk register. if the ddr bit is 0 (input) the buffered pin input is read. if the ddr bit is 1 (output) the output of the port data register is read. this register is not in the map in peripheral or expanded modes while the emk control bit in mode register is set. therefore, these accesses will be echoed externally. when inputs, these pins can be selected to be high impedance or pulled up, based upon the state of the pupke bit in the pucr register. 76543210 r bit 7 654321 bit 0 w reset 00000000 alternate pin function ecs xcs xab19 xab18 xab17 xab16 xab15 xab14 figure 18-19. port k data register (portk) table 18-13. portk field descriptions field description 7 port k, bit 7 port k, bit 7 ?this bit is used as an emulation chip select signal for the emulation of the internal memory expansion, or as general-purpose i/o, depending upon the state of the emk bit in the mode register. while this bit is used as a chip select, the external bit will return to its de-asserted state (v dd ) for approximately 1/4 cycle just after the negative edge of eclk, unless the external access is stretched and eclk is free-running (estr bit in ebictl = 0). see the mmc block description chapter for additional details on when this signal will be active. 6 port k, bit 6 port k, bit 6 ?this bit is used as an external chip select signal for most external accesses that are not selected by ecs (see the mmc block description chapter for more details), depending upon the state the of the emk bit in the mode register. while this bit is used as a chip select, the external pin will return to its de- asserted state (v dd ) for approximately 1/4 cycle just after the negative edge of eclk, unless the external access is stretched and eclk is free-running (estr bit in ebictl = 0). 5:0 port k, bits 5:0 port k, bits 5:0 these six bits are used to determine which flash/rom or external memory array page is being accessed. they can be viewed as expanded addresses xab19?ab14 of the 20-bit address used to access up to1m byte internal flash/rom or external memory array. alternatively, these bits can be used for general-purpose i/o depending upon the state of the emk bit in the mode register. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 532 freescale semiconductor 18.3.2.16 port k data direction register (ddrk) read: anytime write: anytime this register determines the primary direction for each port k pin con?ured as general-purpose i/o. this register is not in the map in peripheral or expanded modes while the emk control bit in mode register is set. therefore, these accesses will be echoed externally. 18.4 functional description 18.4.1 detecting access type from external signals the external signals lstrb, r/ w, and ab0 indicate the type of bus access that is taking place. accesses to the internal ram module are the only type of access that would produce lstrb = ab0 = 1, because the internal ram is speci?ally designed to allow misaligned 16-bit accesses in a single cycle. in these cases the data for the address that was accessed is on the low half of the data bus and the data for address + 1 is on the high half of the data bus. this is summarized in table 18-15 . 76543210 r bit 7 654321 bit 0 w reset 00000000 figure 18-20. port k data direction register (ddrk) table 18-14. ebictl field descriptions field description 7:0 ddrk data direction port k bits 0 associated pin is a high-impedance input 1 associated pin is an output note: it is unwise to write portk and ddrk as a word access. if you are changing port k pins from inputs to outputs, the data may have extra transitions during the write. it is best to initialize portk before enabling as outputs. note: to ensure that you read the correct value from the portk pins, always wait at least one cycle after writing to the ddrk register before reading from the portk register. table 18-15. access type vs. bus control pins lstrb ab0 r/ w type of access 1 0 1 8-bit read of an even address 0 1 1 8-bit read of an odd address 1 0 0 8-bit write of an even address 0 1 0 8-bit write of an odd address 0 0 1 16-bit read of an even address chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 533 18.4.2 stretched bus cycles in order to allow fast internal bus cycles to coexist in a system with slower external memory resources, the hcs12 supports the concept of stretched bus cycles (module timing reference clocks for timers and baud rate generators are not affected by this stretching). control bits in the misc register in the mmc sub-block of the core specify the amount of stretch (0, 1, 2, or 3 periods of the internal bus-rate clock). while stretching, the cpu state machines are all held in their current state. at this point in the cpu bus cycle, write data would already be driven onto the data bus so the length of time write data is valid is extended in the case of a stretched bus cycle. read data would not be captured by the system until the e clock falling edge. in the case of a stretched bus cycle, read data is not required until the speci?d setup time before the falling edge of the stretched e clock. the chip selects, and r/ w signals remain valid during the period of stretching (throughout the stretched e high time). note the address portion of the bus cycle is not stretched . 18.4.3 modes of operation the operating mode out of reset is determined by the states of the modc, modb, and moda pins during reset ( table 18-16 ). the modc, modb, and moda bits in the mode register show the current operating mode and provide limited mode switching during operation. the states of the modc, modb, and moda pins are latched into these bits on the rising edge of the reset signal. 1 1 1 16-bit read of an odd address (low/high data swapped) 0 0 0 16-bit write to an even address 1 1 0 16-bit write to an odd address (low/high data swapped) table 18-16. mode selection modc modb moda mode description 0 0 0 special single chip, bdm allowed and active. bdm is allowed in all other modes but a serial command is required to make bdm active. 0 0 1 emulation expanded narrow, bdm allowed 0 1 0 special test (expanded wide), bdm allowed 0 1 1 emulation expanded wide, bdm allowed 1 0 0 normal single chip, bdm allowed 1 0 1 normal expanded narrow, bdm allowed 1 1 0 peripheral; bdm allowed but bus operations would cause bus con?cts (must not be used) 1 1 1 normal expanded wide, bdm allowed table 18-15. access type vs. bus control pins lstrb ab0 r/ w type of access chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 534 freescale semiconductor there are two basic types of operating modes: 1. normal modes: some registers and bits are protected against accidental changes. 2. special modes: allow greater access to protected control registers and bits for special purposes such as testing. a system development and debug feature, background debug mode (bdm), is available in all modes. in special single-chip mode, bdm is active immediately after reset. some aspects of port e are not mode dependent. bit 1 of port e is a general purpose input or the irq interrupt input. irq can be enabled by bits in the cpu s condition codes register but it is inhibited at reset so this pin is initially con?ured as a simple input with a pull-up. bit 0 of port e is a general purpose input or the xirq interrupt input. xirq can be enabled by bits in the cpu s condition codes register but it is inhibited at reset so this pin is initially con?ured as a simple input with a pull-up. the estr bit in the ebictl register is set to one by reset in any user mode. this assures that the reset vector can be fetched even if it is located in an external slow memory device. the pe6/modb/ipipe1 and pe5/moda/ipipe0 pins act as high-impedance mode select inputs during reset. the following paragraphs discuss the default bus setup and describe which aspects of the bus can be changed after reset on a per mode basis. 18.4.3.1 normal operating modes these modes provide three operating con?urations. background debug is available in all three modes, but must ?st be enabled for some operations by means of a bdm background command, then activated. 18.4.3.1.1 normal single-chip mode there is no external expansion bus in this mode. all pins of ports a, b and e are con?ured as general purpose i/o pins port e bits 1 and 0 are available as general purpose input only pins with internal pull resistors enabled. all other pins of port e are bidirectional i/o pins that are initially con?ured as high-impedance inputs with internal pull resistors enabled. ports a and b are con?ured as high-impedance inputs with their internal pull resistors disabled. the pins associated with port e bits 6, 5, 3, and 2 cannot be con?ured for their alternate functions ipipe1, ipipe0, lstrb, and r/ w while the mcu is in single chip modes. in single chip modes, the associated control bits pipoe, lstre, and rdwe are reset to zero. writing the opposite state into them in single chip mode does not change the operation of the associated port e pins. in normal single chip mode, the mode register is writable one time. this allows a user program to change the bus mode to narrow or wide expanded mode and/or turn on visibility of internal accesses. port e, bit 4 can be con?ured for a free-running e clock output by clearing neclk=0. typically the only use for an e clock output while the mcu is in single chip modes would be to get a constant speed clock for use in the external application system. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 535 18.4.3.1.2 normal expanded wide mode in expanded wide modes, ports a and b are con?ured as a 16-bit multiplexed address and data bus and port e bit 4 is con?ured as the e clock output signal. these signals allow external memory and peripheral devices to be interfaced to the mcu. port e pins other than pe4/eclk are con?ured as general purpose i/o pins (initially high-impedance inputs with internal pull resistors enabled). control bits pipoe, neclk, lstre, and rdwe in the pear register can be used to con?ure port e pins to act as bus control outputs instead of general purpose i/o pins. it is possible to enable the pipe status signals on port e bits 6 and 5 by setting the pipoe bit in pear, but it would be unusual to do so in this mode. development systems where pipe status signals are monitored would typically use the special variation of this mode. the port e bit 2 pin can be recon?ured as the r/ w bus control signal by writing ? to the rdwe bit in pear. if the expanded system includes external devices that can be written, such as ram, the rdwe bit would need to be set before any attempt to write to an external location. if there are no writable resources in the external system, pe2 can be left as a general purpose i/o pin. the port e bit 3 pin can be recon?ured as the lstrb bus control signal by writing ? to the lstre bit in pear. the default condition of this pin is a general purpose input because the lstrb function is not needed in all expanded wide applications. the port e bit 4 pin is initially con?ured as eclk output with stretch. the e clock output function depends upon the settings of the neclk bit in the pear register, the ivis bit in the mode register and the estr bit in the ebictl register. the e clock is available for use in external select decode logic or as a constant speed clock for use in the external application system. 18.4.3.1.3 normal expanded narrow mode this mode is used for lower cost production systems that use 8-bit wide external eproms or rams. such systems take extra bus cycles to access 16-bit locations but this may be preferred over the extra cost of additional external memory devices. ports a and b are con?ured as a 16-bit address bus and port a is multiplexed with data. internal visibility is not available in this mode because the internal cycles would need to be split into two 8-bit cycles. since the pear register can only be written one time in this mode, use care to set all bits to the desired states during the single allowed write. the pe3/ lstrb pin is always a general purpose i/o pin in normal expanded narrow mode. although it is possible to write the lstre bit in pear to ??in this mode, the state of lstre is overridden and port e bit 3 cannot be recon?ured as the lstrb output. it is possible to enable the pipe status signals on port e bits 6 and 5 by setting the pipoe bit in pear, but it would be unusual to do so in this mode. lstrb would also be needed to fully understand system activity. development systems where pipe status signals are monitored would typically use special expanded wide mode or occasionally special expanded narrow mode. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 536 freescale semiconductor the pe4/eclk pin is initially con?ured as eclk output with stretch. the e clock output function depends upon the settings of the neclk bit in the pear register, the ivis bit in the mode register and the estr bit in the ebictl register. in normal expanded narrow mode, the e clock is available for use in external select decode logic or as a constant speed clock for use in the external application system. the pe2/r/w pin is initially con?ured as a general purpose input with an internal pull resistor enabled but this pin can be recon?ured as the r/ w bus control signal by writing ??to the rdwe bit in pear. if the expanded narrow system includes external devices that can be written such as ram, the rdwe bit would need to be set before any attempt to write to an external location. if there are no writable resources in the external system, pe2 can be left as a general purpose i/o pin. 18.4.3.1.4 emulation expanded wide mode in expanded wide modes, ports a and b are con?ured as a 16-bit multiplexed address and data bus and port e provides bus control and status signals. these signals allow external memory and peripheral devices to be interfaced to the mcu. these signals can also be used by a logic analyzer to monitor the progress of application programs. the bus control related pins in port e (pe7/noacc, pe6/modb/ipipe1, pe5/moda/ipipe0, pe4/eclk, pe3/ lstrb/ t a glo, and pe2/r/ w) are all con?ured to serve their bus control output functions rather than general purpose i/o. notice that writes to the bus control enable bits in the pear register in emulation mode are restricted. 18.4.3.1.5 emulation expanded narrow mode expanded narrow modes are intended to allow connection of single 8-bit external memory devices for lower cost systems that do not need the performance of a full 16-bit external data bus. accesses to internal resources that have been mapped external (i.e. porta, portb, ddra, ddrb, porte, ddre, pear, pucr, rdriv) will be accessed with a 16-bit data bus on ports a and b. accesses of 16-bit external words to addresses which are normally mapped external will be broken into two separate 8-bit accesses using port a as an 8-bit data bus. internal operations continue to use full 16-bit data paths. they are only visible externally as 16-bit information if ivis=1. ports a and b are configured as multiplexed address and data output ports. during external accesses, address a15, data d15 and d7 are associated with pa7, address a0 is associated with pb0 and data d8 and d0 are associated with pa0. during internal visible accesses and accesses to internal resources that have been mapped external, address a15 and data d15 is associated with pa7 and address a0 and data d0 is associated with pb0. the bus control related pins in port e (pe7/noacc, pe6/modb/ipipe1, pe5/moda/ipipe0, pe4/eclk, pe3/ lstrb/ taglo, and pe2/r/ w) are all configured to serve their bus control output functions rather than general purpose i/o. notice that writes to the bus control enable bits in the pear register in emulation mode are restricted. the main difference between special modes and normal modes is that some of the bus control and system control signals cannot be written in emulation modes. chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 537 18.4.3.2 special operating modes there are two special operating modes that correspond to normal operating modes. these operating modes are commonly used in factory testing and system development. 18.4.3.2.1 special single-chip mode when the mcu is reset in this mode, the background debug mode is enabled and active. the mcu does not fetch the reset vector and execute application code as it would in other modes. instead the active background mode is in control of cpu execution and bdm firmware is waiting for additional serial commands through the bkgd pin. when a serial command instructs the mcu to return to normal execution, the system will be configured as described below unless the reset states of internal control registers have been changed through background commands after the mcu was reset. there is no external expansion bus after reset in this mode. ports a and b are initially simple bidirectional i/o pins that are configured as high-impedance inputs with internal pull resistors disabled; however, writing to the mode select bits in the mode register (which is allowed in special modes) can change this after reset. all of the port e pins (except pe4/eclk) are initially configured as general purpose high-impedance inputs with internal pull resistors enabled. pe4/eclk is configured as the e clock output in this mode. the pins associated with port e bits 6, 5, 3, and 2 cannot be configured for their alternate functions ipipe1, ipipe0, lstrb, and r/ w while the mcu is in single chip modes. in single chip modes, the associated control bits pipoe, lstre and rdwe are reset to zero. writing the opposite value into these bits in single chip mode does not change the operation of the associated port e pins. port e, bit 4 can be configured for a free-running e clock output by clearing neclk=0. typically the only use for an e clock output while the mcu is in single chip modes would be to get a constant speed clock for use in the external application system. 18.4.3.2.2 special test mode in expanded wide modes, ports a and b are configured as a 16-bit multiplexed address and data bus and port e provides bus control and status signals. in special test mode, the write protection of many control bits is lifted so that they can be thoroughly tested without needing to go through reset. 18.4.3.3 test operating mode there is a test operating mode in which an external master, such as an i.c. tester, can control the on-chip peripherals. 18.4.3.3.1 peripheral mode this mode is intended for factory testing of the mcu. in this mode, the cpu is inactive and an external (tester) bus master drives address, data and bus control signals in through ports a, b and e. in effect, the whole mcu acts as if it was a peripheral under control of an external cpu. this allows faster testing of on-chip memory and peripherals than previous testing methods. since the mode control register is not accessible in peripheral mode, the only way to change to another mode is to reset the mcu into a different chapter 18 multiplexed external bus interface (mebiv3) mc9s12kg128 data sheet, rev. 1.15 538 freescale semiconductor mode. background debugging should not be used while the mcu is in special peripheral mode as internal bus conflicts between bdm and the external master can cause improper operation of both functions. 18.4.4 internal visibility internal visibility is available when the mcu is operating in expanded wide modes or emulation narrow mode. it is not available in single-chip, peripheral or normal expanded narrow modes. internal visibility is enabled by setting the ivis bit in the mode register. if an internal access is made while e, r/ w, and lstrb are con?ured as bus control outputs and internal visibility is off (ivis=0), e will remain low for the cycle, r/ w will remain high, and address, data and the lstrb pins will remain at their previous state. when internal visibility is enabled (ivis=1), certain internal cycles will be blocked from going external. during cycles when the bdm is selected, r/ w will remain high, data will maintain its previous state, and address and lstrb pins will be updated with the internal value. during cpu no access cycles when the bdm is not driving, r/ w will remain high, and address, data and the lstrb pins will remain at their previous state. note when the system is operating in a secure mode, internal visibility is not available (i.e., ivis = 1 has no effect). also, the ipipe signals will not be visible, regardless of operating mode. ipipe1?pipe0 will display 0es if they are enabled. in addition, the mod bits in the mode control register cannot be written. 18.4.5 low-power options the mebi does not contain any user-controlled options for reducing power consumption. the operation of the mebi in low-power modes is discussed in the following subsections. 18.4.5.1 operation in run mode the mebi does not contain any options for reducing power in run mode; however, the external addresses are conditioned to reduce power in single-chip modes. expanded bus modes will increase power consumption. 18.4.5.2 operation in wait mode the mebi does not contain any options for reducing power in wait mode. 18.4.5.3 operation in stop mode the mebi will cease to function after execution of a cpu stop instruction. mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 539 chapter 19 module mapping control (mmcv4) 19.1 introduction this section describes the functionality of the module mapping control (mmc) sub-block of the s12 core platform. the block diagram of the mmc is shown in figure 19-1 . figure 19-1. mmc block diagram the mmc is the sub-module which controls memory map assignment and selection of internal resources and external space. internal buses between the core and memories and between the core and peripherals is controlled in this module. the memory expansion is generated in this module. mmc mode information registers cpu write data bus cpu address bus cpu control stop, wait address decode cpu read data bus ebi alternate address bus ebi alternate write data bus ebi alternate read data bus security clocks, reset read & write enables alternate address bus (bdm) alternate write data bus (bdm) alternate read data bus (bdm) core select (s) port k interface memory space select(s) peripheral select bus control secure bdm_unsecure mmc_secure internal memory expansion chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 540 freescale semiconductor 19.1.1 features registers for mapping of address space for on-chip ram, eeprom, and flash (or rom) memory blocks and associated registers memory mapping control and selection based upon address decode and system operating mode core address bus control core data bus control and multiplexing core security state decoding emulation chip select signal generation ( ecs) external chip select signal generation ( xcs) internal memory expansion external stretch and rom mapping control functions via the misc register reserved registers for test purposes con?urable system memory options de?ed at integration of core into the system-on-a-chip (soc). 19.1.2 modes of operation some of the registers operate differently depending on the mode of operation (i.e., normal expanded wide, special single chip, etc.). this is best understood from the register descriptions. 19.2 external signal description all interfacing with the mmc sub-block is done within the core, it has no external signals. 19.3 memory map and register de?ition a summary of the registers associated with the mmc sub-block is shown in figure 19-2 . detailed descriptions of the registers and bits are given in the subsections that follow. 19.3.1 module memory map table 19-1. mmc memory map address offset register access initialization of internal ram position register (initrm) r/w initialization of internal registers position register (initrg) r/w initialization of internal eeprom position register (initee) r/w miscellaneous system control register (misc) r/w reserved . . . . chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 541 reserved . . . . memory size register 0 (memsiz0) r memory size register 1 (memsiz1) r . . . . program page index register (ppage) r/w reserved table 19-1. mmc memory map (continued) address offset register access chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 542 freescale semiconductor 19.3.2 register descriptions 19.3.2.1 initialization of internal ram position register (initrm) read: anytime name bit 7 6 5 4321 bit 0 initrm r ram15 ram14 ram13 ram12 ram11 00 ramhal w initrg r 0 reg14 reg13 reg12 reg11 000 w initee r ee15 ee14 ee13 ee12 ee11 00 eeon w misc r 0 0 0 0 exstr1 exstr0 romhm romon w mtsto r bit 7 6 5 4321 bit 0 w mtst1 r bit 7 6 5 4321 bit 0 w memsiz0 r reg_sw0 0 eep_sw1 eep_sw0 0 ram_sw2 ram_sw1 ram_sw0 w memsiz1 r rom_sw1 rom_sw0 0 0 0 0 pag_sw1 pag_sw0 w ppage r 0 0 pix5 pix4 pix3 pix2 pix1 pix0 w reserved r 0 0 0 00000 w = unimplemented figure 19-2. mmc register summary 76543210 r ram15 ram14 ram13 ram12 ram11 00 ramhal w reset 0 0 0 01001 = unimplemented or reserved figure 19-3. initialization of internal ram position register (initrm) chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 543 write: once in normal and emulation modes, anytime in special modes note writes to this register take one cycle to go into effect. this register initializes the position of the internal ram within the on-chip system memory map. table 19-2. initrm field descriptions field description 7:3 ram[15:11] internal ram map position ?these bits determine the upper ?e bits of the base address for the system s internal ram array. 0 ramhal ram high-align ?ramhal speci?s the alignment of the internal ram array. 0 aligns the ram to the lowest address (0x0000) of the mappable space 1 aligns the ram to the higher address (0xffff) of the mappable space chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 544 freescale semiconductor 19.3.2.2 initialization of internal registers position register (initrg) read: anytime write: once in normal and emulation modes and anytime in special modes this register initializes the position of the internal registers within the on-chip system memory map. the registers occupy either a 1k byte or 2k byte space and can be mapped to any 2k byte space within the ?st 32k bytes of the system s address space. 76543210 r0 reg14 reg13 reg12 reg11 000 w reset 0 0 0 00000 = unimplemented or reserved figure 19-4. initialization of internal registers position register (initrg) table 19-3. initrg field descriptions field description 6:3 reg[14:11] internal register map position ?these four bits in combination with the leading zero supplied by bit 7 of initrg determine the upper ?e bits of the base address for the system s internal registers (i.e., the minimum base address is 0x0000 and the maximum is 0x7fff). chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 545 19.3.2.3 initialization of internal eeprom position register (initee) read: anytime write: the eeon bit can be written to any time on all devices. bits e[11:15] are ?rite anytime in all modes on most devices. on some devices, bits e[11:15] are ?rite once in normal and emulation modes and write anytime in special modes? see device overview chapter to determine the actual write access rights. note writes to this register take one cycle to go into effect. this register initializes the position of the internal eeprom within the on-chip system memory map. 76543210 r ee15 ee14 ee13 ee12 ee11 00 eeon w reset 1 1. the reset state of this register is controlled at chip integration. please refer to the device overview section to determine the actual reset state of this register. = unimplemented or reserved figure 19-5. initialization of internal eeprom position register (initee) table 19-4. initee field descriptions field description 7:3 ee[15:11] internal eeprom map position these bits determine the upper ?e bits of the base address for the system s internal eeprom array. 0 eeon enable eeprom ?this bit is used to enable the eeprom memory in the memory map. 0 disables the eeprom from the memory map. 1 enables the eeprom in the memory map at the address selected by ee[15:11]. chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 546 freescale semiconductor 19.3.2.4 miscellaneous system control register (misc) read: anytime write: as stated in each bit description note writes to this register take one cycle to go into effect. this register initializes miscellaneous control functions. 76543210 r0000 exstr1 exstr0 romhm romon w reset: expanded or emulation 0000110 1 reset: peripheral or single chip 00001101 reset: special test 00001100 1. the reset state of this bit is determined at the chip integration level. = unimplemented or reserved figure 19-6. miscellaneous system control register (misc) table 19-5. initee field descriptions field description 3:2 exstr[1:0] external access stretch bits 1 and 0 write: once in normal and emulation modes and anytime in special modes this two-bit ?ld determines the amount of clock stretch on accesses to the external address space as shown in table 19-6 . in single chip and peripheral modes these bits have no meaning or effect. 1 romhm flash eeprom or rom only in second half of memory map write: once in normal and emulation modes and anytime in special modes 0 the ?ed page(s) of flash eeprom or rom in the lower half of the memory map can be accessed. 1 disables direct access to the flash eeprom or rom in the lower half of the memory map. these physical locations of the flash eeprom or rom remain accessible through the program page window. 0 romon romon ?enable flash eeprom or rom write: once in normal and emulation modes and anytime in special modes this bit is used to enable the flash eeprom or rom memory in the memory map. 0 disables the flash eeprom or rom from the memory map. 1 enables the flash eeprom or rom in the memory map. table 19-6. external stretch bit de?ition stretch bit exstr1 stretch bit exstr0 number of e clocks stretched 00 0 01 1 10 2 11 3 chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 547 19.3.2.5 reserved test register 0 (mtst0) read: anytime write: no effect ?this register location is used for internal test purposes. 19.3.2.6 reserved test register 1 (mtst1) read: anytime write: no effect ?this register location is used for internal test purposes. 76543210 r00000000 w reset 0 0 0 00000 = unimplemented or reserved figure 19-7. reserved test register 0 (mtst0) 76543210 r00000000 w reset 0 0 0 10000 = unimplemented or reserved figure 19-8. reserved test register 1 (mtst1) chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 548 freescale semiconductor 19.3.2.7 memory size register 0 (memsiz0) read: anytime write: writes have no effect reset: de?ed at chip integration, see device overview section. the memsiz0 register re?cts the state of the register, eeprom and ram memory space con?uration switches at the core boundary which are con?ured at system integration. this register allows read visibility to the state of these switches. 76543210 r reg_sw0 0 eep_sw1 eep_sw0 0 ram_sw2 ram_sw1 ram_sw0 w reset = unimplemented or reserved figure 19-9. memory size register 0 (memsiz0) table 19-7. memsiz0 field descriptions field description 7 reg_sw0 allocated system register space 0 allocated system register space size is 1k byte 1 allocated system register space size is 2k byte 5:4 eep_sw[1:0] allocated system eeprom memory space ?the allocated system eeprom memory space size is as given in table 19-8 . 2 ram_sw[2:0] allocated system ram memory space ?the allocated system ram memory space size is as given in table 19-9 . table 19-8. allocated eeprom memory space eep_sw1:eep_sw0 allocated eeprom space 00 0k byte 01 2k bytes 10 4k bytes 11 8k bytes table 19-9. allocated ram memory space ram_sw2:ram_sw0 allocated ram space ram mappable region initrm bits used ram reset base address 1 000 2k bytes 2k bytes ram[15:11] 0x0800 001 4k bytes 4k bytes ram[15:12] 0x0000 010 6k bytes 8k bytes 2 ram[15:13] 0x0800 011 8k bytes 8k bytes ram[15:13] 0x0000 100 10k bytes 16k bytes 2 ram[15:14] 0x1800 chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 549 note as stated, the bits in this register provide read visibility to the system physical memory space allocations de?ed at system integration. the actual array size for any given type of memory block may differ from the allocated size. please refer to the device overview chapter for actual sizes. 19.3.2.8 memory size register 1 (memsiz1) read: anytime write: writes have no effect reset: de?ed at chip integration, see device overview section. the memsiz1 register re?cts the state of the flash or rom physical memory space and paging switches at the core boundary which are con?ured at system integration. this register allows read visibility to the state of these switches. 101 12k bytes 16k bytes 2 ram[15:14] 0x1000 110 14k bytes 16k bytes 2 ram[15:14] 0x0800 111 16k bytes 16k bytes ram[15:14] 0x0000 1 the ram reset base address is based on the reset value of the initrm register, 0x0009. 2 alignment of the allocated ram space within the ram mappable region is dependent on the value of ramhal. 76543210 r rom_sw1 rom_sw0 0 0 0 0 pag_sw1 pag_sw0 w reset = unimplemented or reserved figure 19-10. memory size register 1 (memsiz1) table 19-10. memsiz0 field descriptions field description 7:6 rom_sw[1:0] allocated system flash or rom physical memory space ?the allocated system flash or rom physical memory space is as given in table 19-11 . 1:0 pag_sw[1:0] allocated off-chip flash or rom memory space the allocated off-chip flash or rom memory space size is as given in table 19-12 . table 19-9. allocated ram memory space (continued) ram_sw2:ram_sw0 allocated ram space ram mappable region initrm bits used ram reset base address 1 chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 550 freescale semiconductor note as stated, the bits in this register provide read visibility to the system memory space and on-chip/off-chip partitioning allocations de?ed at system integration. the actual array size for any given type of memory block may differ from the allocated size. please refer to the device overview chapter for actual sizes. 19.3.2.9 program page index register (ppage) read: anytime write: determined at chip integration. generally it s: ?rite anytime in all modes; on some devices it will be: ?rite only in special modes.?check speci? device documentation to determine which applies. reset: de?ed at chip integration as either 0x00 (paired with write in any mode) or 0x3c (paired with write only in special modes), see device overview chapter. table 19-11. allocated flash/rom physical memory space rom_sw1:rom_sw0 allocated flash or rom space 00 0k byte 01 16k bytes 10 48k bytes (1) 11 64k bytes (1) notes: 1. the romhm software bit in the misc register determines the accessibility of the flash/rom memory space. please refer to section 19.3.2.8, ?emory size register 1 (memsiz1) , for a detailed functional description of the romhm bit. table 19-12. allocated off-chip memory options pag_sw1:pag_sw0 off-chip space on-chip space 00 876k bytes 128k bytes 01 768k bytes 256k bytes 10 512k bytes 512k bytes 11 0k byte 1m byte 76543210 r0 0 pix5 pix4 pix3 pix2 pix1 pix0 w reset 1 1. the reset state of this register is controlled at chip integration. please refer to the device overview section to determine the actual reset state of this register. = unimplemented or reserved figure 19-11. program page index register (ppage) chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 551 the hcs12 core architecture limits the physical address space available to 64k bytes. the program page index register allows for integrating up to 1m byte of flash or rom into the system by using the six page index bits to page 16k byte blocks into the program page window located from 0x8000 to 0xbfff as de?ed in table 19-14 . call and rtc instructions have special access to read and write this register without using the address bus. note normal writes to this register take one cycle to go into effect. writes to this register using the special access of the call and rtc instructions will be complete before the end of the associated instruction. 19.4 functional description the mmc sub-block performs four basic functions of the core operation: bus control, address decoding and select signal generation, memory expansion, and security decoding for the system. each aspect is described in the following subsections. 19.4.1 bus control the mmc controls the address bus and data buses that interface the core with the rest of the system. this includes the multiplexing of the input data buses to the core onto the main cpu read data bus and control table 19-13. memsiz0 field descriptions field description 5:0 pix[5:0] program page index bits 5:0 ?these page index bits are used to select which of the 64 flash or rom array pages is to be accessed in the program page window as shown in table 19-14 . table 19-14. program page index register bits pix5 pix4 pix3 pix2 pix1 pix0 program space selected 000000 16k page 0 000001 16k page 1 000010 16k page 2 000011 16k page 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111100 16k page 60 111101 16k page 61 111110 16k page 62 111111 16k page 63 chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 552 freescale semiconductor of data ?w from the cpu to the output address and data buses of the core. in addition, the mmc manages all cpu read data bus swapping operations. 19.4.2 address decoding as data ?ws on the core address bus, the mmc decodes the address information, determines whether the internal core register or ?mware space, the peripheral space or a memory register or array space is being addressed and generates the correct select signal. this decoding operation also interprets the mode of operation of the system and the state of the mapping control registers in order to generate the proper select. the mmc also generates two external chip select signals, emulation chip select ( ecs) and external chip select ( xcs). 19.4.2.1 select priority and mode considerations although internal resources such as control registers and on-chip memory have default addresses, each can be relocated by changing the default values in control registers. normally, i/o addresses, control registers, vector spaces, expansion windows, and on-chip memory are mapped so that their address ranges do not overlap. the mmc will make only one select signal active at any given time. this activation is based upon the priority outlined in table 19-15 . if two or more blocks share the same address space, only the select signal for the block with the highest priority will become active. an example of this is if the registers and the ram are mapped to the same space, the registers will have priority over the ram and the portion of ram mapped in this shared space will not be accessible. the expansion windows have the lowest priority. this means that registers, vectors, and on-chip memory are always visible to a program regardless of the values in the page select registers. in expanded modes, all address space not used by internal resources is by default external memory space. the data registers and data direction registers for ports a and b are removed from the on-chip memory map and become external accesses. if the eme bit in the mode register (see mebi block description chapter) is set, the data and data direction registers for port e are also removed from the on-chip memory map and become external accesses. in special peripheral mode, the ?st 16 registers associated with bus expansion are removed from the on-chip memory map (porta, portb, ddra, ddrb, porte, ddre, pear, mode, pucr, rdriv, and the ebi reserved registers). table 19-15. select signal priority priority address space highest bdm (internal to core) ?mware or register space ... internal register space ... ram memory block ... eeprom memory block ... on-chip flash or rom lowest remaining external space chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 553 in emulation modes, if the emk bit in the mode register (see mebi block description chapter) is set, the data and data direction registers for port k are removed from the on-chip memory map and become external accesses. 19.4.2.2 emulation chip select signal when the emk bit in the mode register (see mebi block description chapter) is set, port k bit 7 is used as an active-low emulation chip select signal, ecs. this signal is active when the system is in emulation mode, the emk bit is set and the flash or rom space is being addressed subject to the conditions outlined in section 19.4.3.2, ?xtended address (xab19:14) and ecs signal functionality . when the emk bit is clear, this pin is used for general purpose i/o. 19.4.2.3 external chip select signal when the emk bit in the mode register (see mebi block description chapter) is set, port k bit 6 is used as an active-low external chip select signal, xcs. this signal is active only when the ecs signal described above is not active and when the system is addressing the external address space. accesses to unimplemented locations within the register space or to locations that are removed from the map (i.e., ports a and b in expanded modes) will not cause this signal to become active. when the emk bit is clear, this pin is used for general purpose i/o. 19.4.3 memory expansion the hcs12 core architecture limits the physical address space available to 64k bytes. the program page index register allows for integrating up to 1m byte of flash or rom into the system by using the six page index bits to page 16k byte blocks into the program page window located from 0x8000 to 0xbfff in the physical memory space. the paged memory space can consist of solely on-chip memory or a combination of on-chip and off-chip memory. this partitioning is con?ured at system integration through the use of the paging con?uration switches ( pag_sw1:pag_sw0 ) at the core boundary. the options available to the integrator are as given in table 19-16 (this table matches table 19-12 but is repeated here for easy reference). based upon the system con?uration, the program page window will consider its access to be either internal or external as de?ed in table 19-17 . table 19-16. allocated off-chip memory options pag_sw1:pag_sw0 off-chip space on-chip space 00 876k bytes 128k bytes 01 768k bytes 256k bytes 10 512k bytes 512k bytes 11 0k byte 1m byte chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 554 freescale semiconductor note the partitioning as de?ed in table 19-17 applies only to the allocated memory space and the actual on-chip memory sizes implemented in the system may differ. please refer to the device overview chapter for actual sizes. the ppage register holds the page select value for the program page window. the value of the ppage register can be manipulated by normal read and write (some devices don t allow writes in some modes) instructions as well as the call and rtc instructions. control registers, vector spaces, and a portion of on-chip memory are located in unpaged portions of the 64k byte physical address space. the stack and i/o addresses should also be in unpaged memory to make them accessible from any page. the starting address of a service routine must be located in unpaged memory because the 16-bit exception vectors cannot point to addresses in paged memory. however, a service routine can call other routines that are in paged memory. the upper 16k byte block of memory space (0xc000?xffff) is unpaged. it is recommended that all reset and interrupt vectors point to locations in this area. 19.4.3.1 call and return from call instructions call and rtc are uninterruptable instructions that automate page switching in the program expansion window. call is similar to a jsr instruction, but the subroutine that is called can be located anywhere in the normal 64k byte address space or on any page of program expansion memory. call calculates and stacks a return address, stacks the current ppage value, and writes a new instruction-supplied value to ppage. the ppage value controls which of the 64 possible pages is visible through the 16k byte expansion window in the 64k byte memory map. execution then begins at the address of the called subroutine. during the execution of a call instruction, the cpu: writes the old ppage value into an internal temporary register and writes the new instruction-supplied ppage value into the ppage register. table 19-17. external/internal page window access pag_sw1:pag_sw0 partitioning pix5:0 value page window access 00 876k off-chip, 128k on-chip 0x0000?x0037 external 0x0038?x003f internal 01 768k off-chip, 256k on-chip 0x0000?x002f external 0x0030?x003f internal 10 512k off-chip, 512k on-chip 0x0000?x001f external 0x0020?x003f internal 11 0k off-chip, 1m on-chip n/a external 0x0000?x003f internal chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 555 calculates the address of the next instruction after the call instruction (the return address), and pushes this 16-bit value onto the stack. pushes the old ppage value onto the stack. calculates the effective address of the subroutine, re?ls the queue, and begins execution at the new address on the selected page of the expansion window. this sequence is uninterruptable; there is no need to inhibit interrupts during call execution. a call can be performed from any address in memory to any other address. the ppage value supplied by the instruction is part of the effective address. for all addressing mode variations except indexed-indirect modes, the new page value is provided by an immediate operand in the instruction. in indexed-indirect variations of call, a pointer speci?s memory locations where the new page value and the address of the called subroutine are stored. using indirect addressing for both the new page value and the address within the page allows values calculated at run time rather than immediate values that must be known at the time of assembly. the rtc instruction terminates subroutines invoked by a call instruction. rtc unstacks the ppage value and the return address and re?ls the queue. execution resumes with the next instruction after the call. during the execution of an rtc instruction, the cpu: pulls the old ppage value from the stack pulls the 16-bit return address from the stack and loads it into the pc writes the old ppage value into the ppage register re?ls the queue and resumes execution at the return address this sequence is uninterruptable; an rtc can be executed from anywhere in memory, even from a different page of extended memory in the expansion window. the call and rtc instructions behave like jsr and rts, except they use more execution cycles. therefore, routinely substituting call/rtc for jsr/rts is not recommended. jsr and rts can be used to access subroutines that are on the same page in expanded memory. however, a subroutine in expanded memory that can be called from other pages must be terminated with an rtc. and the rtc unstacks a ppage value. so any access to the subroutine, even from the same page, must use a call instruction so that the correct ppage value is in the stack. 19.4.3.2 extended address (xab19:14) and ecs signal functionality if the emk bit in the mode register is set (see mebi block description chapter) the pix5:0 values will be output on xab19:14 respectively (port k bits 5:0) when the system is addressing within the physical program page window address space (0x8000?xbfff) and is in an expanded mode. when addressing anywhere else within the physical address space (outside of the paging space), the xab19:14 signals will be assigned a constant value based upon the physical address space selected. in addition, the active-low emulation chip select signal, ecs, will likewise function based upon the assigned memory allocation. in the cases of 48k byte and 64k byte allocated physical flash/rom space, the operation of the ecs signal will additionally depend upon the state of the romhm bit (see section 19.3.2.4, ?iscellaneous system control register (misc) ? in the misc register. table 19-18 , table 19-19 , table 19-20 , and chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 556 freescale semiconductor table 19-21 summarize the functionality of these signals based upon the allocated memory con?uration. again, this signal information is only available externally when the emk bit is set and the system is in an expanded mode. table 19-18. 0k byte physical flash/rom allocated address space page window access romhm ecs xab19:14 0x0000?x3fff n/a n/a 1 0x3d 0x4000?x7fff n/a n/a 1 0x3e 0x8000?xbfff n/a n/a 0 pix[5:0] 0xc000?xffff n/a n/a 0 0x3f table 19-19. 16k byte physical flash/rom allocated address space page window access romhm ecs xab19:14 0x0000?x3fff n/a n/a 1 0x3d 0x4000?x7fff n/a n/a 1 0x3e 0x8000?xbfff n/a n/a 1 pix[5:0] 0xc000?xffff n/a n/a 0 0x3f table 19-20. 48k byte physical flash/rom allocated address space page window access romhm ecs xab19:14 0x0000?x3fff n/a n/a 1 0x3d 0x4000?x7fff n/a 0 0 0x3e n/a 1 1 0x8000?xbfff external n/a 1 pix[5:0] internal n/a 0 0xc000?xffff n/a n/a 0 0x3f table 19-21. 64k byte physical flash/rom allocated address space page window access romhm ecs xab19:14 0x0000?x3fff n/a 0 0 0x3d n/a 1 1 0x4000?x7fff n/a 0 0 0x3e n/a 1 1 0x8000?xbfff external n/a 1 pix[5:0] internal n/a 0 0xc000?xffff n/a n/a 0 0x3f chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 557 a graphical example of a memory paging for a system con?ured as 1m byte on-chip flash/rom with 64k allocated physical space is given in figure 19-12 . figure 19-12. memory paging example: 1m byte on-chip flash/rom, 64k allocation these 16k flash/rom pages accessible from 0x0000 to 0x7fff if selected by the romhm bit in the misc register. normal single chip one 16k flash/rom page accessible at a time (selected by ppage = 0 to 63) 0x0000 0x8000 0xff00 0xffff 0x4000 0xc000 59 62 63 60 61 62 63 0123 61 16k flash (unpaged) 16k flash (unpaged) 16k flash (paged) 16k flash (unpaged) vectors chapter 19 module mapping control (mmcv4) mc9s12kg128 data sheet, rev. 1.15 558 freescale semiconductor appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 559 appendix a electrical characteristics a.1 general note the electrical characteristics given in this section are preliminary and should be used as a guide only. values cannot be guaranteed by freescale and are subject to change without notice. this supplement contains the most accurate electrical information for the mc9s12kg128 microcontroller available at the time of publication. the information should be considered preliminary and is subject to change. this introduction is intended to give an overview on several common topics like power supply, current injection, etc. a.1.1 parameter classi?ation the electrical parameters shown in this supplement are guaranteed by various methods. to give the customer a better understanding the following classi?ation is used and the parameters are tagged accordingly in the tables where appropriate. note this classi?ation is shown in the column labeled ??in the parameter tables where appropriate. p: those parameters are guaranteed during production testing on each individual device. c: those parameters are achieved by the design characterization by measuring a statistically relevant sample size across process variations. they are regularly veri?d by production monitors. t: those parameters are achieved by design characterization on a small sample size from typical devices. all values shown in the typical column are within this category. d: those parameters are derived mainly from simulations. a.1.2 power supply the mc9s12kg128 utilizes several pins to supply power to the i/o ports, a/d converter, oscillator, pll and internal logic. the vdda, vssa pair supplies the a/d converter. the vddx, vssx pair supplies the i/o pins. the vddr, vssr pair supplies the internal voltage regulator. vdd1, vss1, vdd2 and vss2 are the supply pins for the digital logic. vddpll, vsspll supply the oscillator and the pll. appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 560 freescale semiconductor vss1 and vss2 are internally connected by metal. vdd1 and vdd2 are internally connected by metal. vdda, vddx, vddr as well as vssa, vssx, vssr are connected by anti-parallel diodes for esd protection. note in the following context vdd5 is used for either vdda, vddr and vddx; vss5 is used for either vssa, vssr and vssx unless otherwise noted. idd5 denotes the sum of the currents ?wing into the vdda, vddx and vddr pins. vdd is used for vdd1, vdd2 and vddpll, vss is used for vss1, vss2 and vsspll. idd is used for the sum of the currents ?wing into vdd1 and vdd2. a.1.3 pins there are four groups of functional pins. a.1.3.1 3.3v/5v i/o pins those i/o pins have a nominal level of 3.3v or 5v depending on the application operating point. this group of pins is comprised of all port i/o pins, the analog inputs, bkgd pin and the reset inputs.the internal structure of all those pins is identical, however some of the functionality may be disabled. e.g. for the analog inputs the output drivers, pull-up and pull-down resistors are disabled permanently. a.1.3.2 analog reference this group of pins is comprised of the vrh and vrl pins. a.1.3.3 oscillator the pins extal, xtal dedicated to the oscillator have a nominal 2.5v level. they are supplied by vddpll. a.1.3.4 pll the pin xfc dedicated to the oscillator have a nominal 2.5v level. it is supplied by vddpll. a.1.3.5 test this pin is used for production testing only. a.1.4 current injection power supply must maintain regulation within operating v dd5 or v dd range during instantaneous and operating maximum current conditions. if positive injection current (v in >v dd5 ) is greater than i dd5 , the injection current may ?w out of vdd5 and could result in external power supply going out of regulation. appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 561 insure external vdd5 load will shunt current greater than maximum injection current. this will be the greatest risk when the mcu is not consuming power; e.g., if no system clock is present, or if clock rate is very low which would reduce overall power consumption. a.1.5 absolute maximum ratings absolute maximum ratings are stress ratings only. a functional operation under or outside those maxima is not guaranteed. stress beyond those limits may affect the reliability or cause permanent damage of the device. this device contains circuitry protecting against damage due to high static voltage or electrical ?lds; however, it is advised that normal precautions be taken to avoid application of any voltages higher than maximum-rated voltages to this high-impedance circuit. reliability of operation is enhanced if unused inputs are tied to an appropriate logic voltage level (e.g., either v ss5 or v dd5 ). table a-1. absolute maximum ratings num rating symbol min max unit 1 i/o, regulator and analog supply voltage v dd5 ?.3 6.5 v 2 internal logic supply voltage 1 1 the device contains an internal voltage regulator to generate the logic and pll supply out of the i/o supply. the absolute maximum ratings apply when the device is powered from an external source. v dd ?.3 3.0 v 3 pll supply voltage 1 v ddpl l ?.3 3.0 v 4 voltage difference vddx to vddr and vdda ? v ddx ?.3 0.3 v 5 voltage difference vssx to vssr and vssa ? v ssx ?.3 0.3 v 6 digital i/o input voltage v in ?.3 6.5 v 7 analog reference v rh , v rl ?.3 6.5 v 8 xfc, extal, xtal inputs v ilv ?.3 3.0 v 9 test input v test ?.3 10.0 v 10 instantaneous maximum current single pin limit for all digital i/o pins 2 2 all digital i/o pins are internally clamped to v ssx and v ddx , v ssr and v ddr or v ssa and v dda . i d ?5 +25 ma 11 instantaneous maximum current single pin limit for xfc, extal, xtal 3 3 these pins are internally clamped to v sspll and v ddpll i dl ?5 +25 ma 12 instantaneous maximum current single pin limit for test 4 4 this pin is clamped low to v ssr , but not clamped high. this pin must be tied low in applications. i dt ?.25 0 ma 13 operating temperature range (packaged) t a ?0 125 c 14 operating temperature range (junction) tj ?0 140 c 15 storage temperature range t stg ?5 155 c appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 562 freescale semiconductor a.1.6 esd protection and latch-up immunity all esd testing is in conformity with cdf-aec-q100 stress test quali?ation for automotive grade integrated circuits. during the device quali?ation esd stresses were performed for the human body model (hbm), the machine model (mm) and the charge device model. a device will be de?ed as a failure if after exposure to esd pulses the device no longer meets the device speci?ation. complete dc parametric and functional testing is performed per the applicable device speci?ation at room temperature followed by hot temperature, unless speci?d otherwise in the device speci?ation. table a-2. esd and latch-up test conditions model description symbol value unit human body series resistance r1 1500 ohm storage capacitance c 100 pf number of pulse per pin positive negative 3 3 machine series resistance r1 0 ohm storage capacitance c 200 pf number of pulse per pin positive negative 3 3 latch-up minimum input voltage limit ?.5 v maximum input voltage limit 7.5 v table a-3. esd and latch-up protection characteristics num c rating symbol min max unit 1 c human body model (hbm) v hbm 2000 v 2 c machine model (mm) v mm 200 v 3 c charge device model (cdm) v cdm 500 v 4 c latch-up current at 125 c positive negative i lat +100 ?00 ma 5 c latch-up current at 27 c positive negative i lat +200 ?00 ma appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 563 a.1.7 operating conditions this chapter describes the operating conditions of the device. unless otherwise noted those conditions apply to all the following data. note instead of specifying ambient temperature all parameters are speci?d for the more meaningful silicon junction temperature. for power dissipation calculations refer to section a.1.8, ?ower dissipation and thermal characteristics . table a-4. operating conditions rating symbol min typ max unit i/o, regulator and analog supply voltage v dd5 3.15 3.3/5 5.5 v internal logic supply voltage 1 1 the device contains an internal voltage regulator to generate the logic and pll supply out of the i/o supply. the absolute maximum ratings apply when this regulator is disabled and the device is powered from an external source. v dd 2.35 2.5 2.75 v pll supply voltage 1 v ddpll 2.35 2.5 2.75 v voltage difference vddx to vdda ? vddx ?.1 0 0.1 v voltage difference vssx to vssr and vssa ? vssx ?.1 0 0.1 v oscillator f osc 0.5 16 mhz bus frequency f bus 0.5 25 mhz mc9s12kg128 c operating junction temperature range t j ?0 100 c operating ambient temperature range 2 2 please refer to section a.1.8, ?ower dissipation and thermal characteristics for more details about the relation between ambient temperature t a and device junction temperature t j . t a ?0 27 85 c mc9s12kg128 v operating junction temperature range t j ?0 120 c operating ambient temperature range 2 t a ?0 27 105 c mc9s12kg128 m operating junction temperature range t j ?0 140 c operating ambient temperature range 2 t a ?0 27 125 c appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 564 freescale semiconductor a.1.8 power dissipation and thermal characteristics power dissipation and thermal characteristics are closely related. the user must assure that the maximum operating junction temperature is not exceeded. the average chip-junction temperature (t j ) in c can be obtained from: the total power dissipation can be calculated from: two cases with internal voltage regulator enabled and disabled must be considered: 1. internal voltage regulator disabled p io is the sum of all output currents on i/o ports associated with vddx and vddr. for r dson is valid: respectively 2. internal voltage regulator enabled i ddr is the current shown in table a-8 and not the overall current ?wing into vddr, which additionally contains the current ?wing into the external loads with output high. p io is the sum of all output currents on i/o ports associated with vddx and vddr. t j t a p d ja ? () + = t j junction temperature, [ c ] = t a ambient temperature, [ c ] = p d total chip power dissipation, [w] = ja package thermal resistance, [ c/w] = p d p int p io + = p int chip internal power dissipation, [w] = p int i dd v dd ? i ddpll v ddpll ? i dda +v dda ? + = p io r dson i i io i 2 ? = r dson v ol i ol ------------ for outputs driven low ; = r dson v dd5 v oh i oh ------------------------------------ for outputs driven high ; = p int i ddr v ddr ? i dda v dda ? + = p io r dson i i io i 2 ? = appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 565 table a-5. thermal package characteristics 1 1 the values for thermal resistance are achieved by package simulations num c rating symbol min typ max unit 1 t thermal resistance lqfp112, single sided pcb 2 2 pc board according to eia/jedec standard 51-2 ja 54 o c/w 2 t thermal resistance lqfp112, double sided pcb with 2 internal planes 3 3 pc board according to eia/jedec standard 51-7 ja 41 o c/w 3 t thermal resistance qfp 80, single sided pcb ja 51 o c/w 4 t thermal resistance qfp 80, double sided pcb with 2 internal planes ja 41 o c/w appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 566 freescale semiconductor a.1.9 i/o characteristics this section describes the characteristics of all 3.3v/5v i/o pins. all parameters are not always applicable, e.g., not all pins feature pull up/down resistances. table a-6. 5v i/o characteristics conditions are shown in table a-4 unless otherwise noted num c rating symbol min typ max unit 1 p input high voltage v ih 0.65*v dd5 ? dd5 + 0.3 v 2 p input low voltage v il v ss5 - 0.3 0.35*v dd5 v 3 c input hysteresis v hys 250 mv 4 p input leakage current (pins in high impedance input mode) v in = v dd5 or v ss5 i in ?.5 2.5 a 5 p output high voltage (pins in output mode) partial drive i oh = ?.0ma full drive i oh = ?0.0ma v oh v dd5 ?0.8 v 6 p output low voltage (pins in output mode) partial drive i ol = +2.0ma full drive i ol = +10.0ma v ol 0.8 v 7 p internal pull up device current, tested at v il max. i pul ?30 a 8 p internal pull up device current, tested at v ih min. i puh 10 a 9 p internal pull down device current, tested at v ih min. i pdh 130 a 10 p internal pull down device current, tested at v il max. i pdl 10 a 11 d input capacitance c in ? pf 12 t injection current 1 single pin limit total device limit. sum of all injected currents 1 refer to section a.1.4, ?urrent injection , for more details i ics i icp ?.5 ?5 2.5 25 ma 13 p port h, j, p interrupt input pulse ?tered 2 2 parameter only applies in stop or pseudo stop mode. t pign 3 s 14 p port h, j, p interrupt input pulse passed 2 t pval 10 s appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 567 table a-7. 3.3v i/o characteristics conditions are shown in table a-4 unless otherwise noted num c rating symbol min typ max unit 1 p input high voltage v ih 0.65*v dd5 ? dd5 + 0.3 v 2 p input low voltage v il v ss5 - 0.3 0.35*v dd5 v 3 c input hysteresis v hys 250 mv 4 p input leakage current (pins in high impedance input mode) v in = v dd5 or v ss5 i in ? 1 a 5 p output high voltage (pins in output mode) partial drive i oh = ?.75ma full drive i oh = ?.0ma v oh v dd5 ?0.4 v 6 p output low voltage (pins in output mode) partial drive i ol = +0.9ma full drive i ol = +4.75ma v ol 0.4 v 7 p internal pull up device current, tested at v il max. i pul ?0 a 8 p internal pull up device current, tested at v ih min. i puh ? a 9 p internal pull down device current, tested at v ih min. i pdh 60 a 10 p internal pull down device current, tested at v il max. i pdl 6 a 11 d input capacitance c in ? pf 12 t injection current 1 single pin limit total device limit. sum of all injected currents 1 refer to section a.1.4, ?urrent injection , for more details i ics i icp ?.5 ?5 2.5 25 ma 13 p port p, j interrupt input pulse ?tered 2 2 parameter only applies in stop or pseudo stop mode. t pulse 3 s 14 p port p, j interrupt input pulse passed 2 t pulse 10 s appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 568 freescale semiconductor a.1.10 supply currents this section describes the current consumption characteristics of the device as well as the conditions for the measurements. 19.4.3.3 measurement conditions all measurements are without output loads. unless otherwise noted the currents are measured in single chip mode, internal voltage regulator enabled and at 25mhz bus frequency using a 4mhz oscillator. 19.4.3.4 additional remarks in expanded modes the currents ?wing in the system are highly dependent on the load at the address, data and control signals as well as on the duty cycle of those signals. no generally applicable numbers can be given. a very good estimate is to take the single chip currents and add the currents due to the external loads. appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 569 table a-8. supply current characteristics conditions are shown in table a-4 unless otherwise noted num rating symbol min typ max unit 1 run supply currents single chip, internal regulator enabled i dd5 65 ma 2 wait supply current all modules enabled only rti enabled 1 1 pll off i ddw 40 5 ma 3 pseudo stop current (rti and cop enabled) 1,2 ?0 c 27 c 70 c 85 c "c" temp option 100 c 105 c "v" temp option 120 c 125 c "m" temp option 140 c i ddps 90 130 155 180 250 295 470 520 1000 350 1200 2400 5000 a 4 pseudo stop current (rti and cop disabled) 1,2 ?0 c 27 c 70 c 85 c "c" temp option 100 c 105 c "v" temp option 120 c 125 c "m" temp option 140 c i ddps 40 80 105 130 200 245 420 470 800 200 1000 2000 5000 a 5 stop current 2 ?0 c 27 c 70 c 85 c "c" temp option 100 c 105 c "v" temp option 120 c 125 c "m" temp option 140 c 2 all those low power dissipation levels t j = t a can be assumed. i dds 20 60 85 110 180 225 400 450 600 100 800 1800 5000 a appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 570 freescale semiconductor a.2 voltage regulator this section describes the characteristics of the on chip voltage regulator. table a-9. vreg_3v3 ?operating conditions num c characteristic symbol min typical max unit 1 p input voltages v vddr,a 3.15 5.5 v 2 p output voltage core full performance mode v dd 2.35 2.5 2.75 v 3 p output voltage pll full performance mode v ddpll 2.35 2.5 2.75 v 4 p low voltage interrupt 1 assert level deassert level 1 monitors v dda , active only in full performance mode. indicates i/o & adc performance degradation due to low supply voltage. v lvia v lvid 4.0 4.15 4.37 4.52 4.66 4.77 v v 5 p low voltage reset 2 assert level deassert level 2 monitors v dd , active only in full performance mode. v lvra and v pord must overlap v lvra v lvrd 2.25 2.55 v v 6 c power-on reset 3 assert level deassert level 3 monitors v dd . active in all modes. the electrical characteristics given in this section are preliminary and should be used as a guide only. values in this section cannot be guaranteed by freescale and are subject to change without notice. v pora v pord 0.97 - 2.05 v v appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 571 a.3 chip power-up and lvi/lvr graphical explanation voltage regulator sub modules lvi (low voltage interrupt), por (power-on reset), and lvr (low voltage reset) handle chip power-up or drops of the supply voltage. their function is described in figure a-1 . figure a-1. voltage regulator ?chip power-up and voltage drops (not scaled) v lvid v lvia v lvrd v lvra v pord lvi por lvr t v v dda v dd lvi enabled lvi disabled due to lvr appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 572 freescale semiconductor a.4 output loads a.4.1 resistive loads the on-chip voltage regulator is intended to supply the internal logic and oscillator circuits allows no external dc loads. a.4.2 capacitive loads the capacitive loads are speci?d in table a-10 . ceramic capacitors with x7r dielectricum are required. table a-10. voltage regulator ?capacitive loads num characteristic symbol min typical max unit 1 vdd external capacitive load c ddext 200 440 12000 nf 2 vddpll external capacitive load c ddpllext 90 220 5000 nf appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 573 a.5 atd characteristics this section describes the characteristics of the analog to digital converter. a.5.1 atd operating characteristics the table a-11 shows conditions under which the atd operates. the following constraints exist to obtain full-scale, full range results: vssa vrl vin vrh vdda . this constraint exists since the sample buffer ampli?r can not drive beyond the power supply levels that it ties to. if the input level goes outside of this range it will effectively be clipped. table a-11. 5v atd operating characteristics conditions are shown in table a-4 unless otherwise noted num c rating symbol min typ max unit 1 d reference potential low high vrl vrh vssa vdda/2 vdda/2 vdda v v 2 c differential reference voltage 1 1 full accuracy is not guaranteed when differential voltage is less than 4.75v vrh-vrl 4.75 5.0 5.25 v 3 d atd clock frequency f atdclk 0.5 2.0 mhz 4 d atd 10-bit conversion period clock cycles 2 conv, time at 2.0mhz atd clock f atdclk conv, time at 4.0mhz 3 atd clock f atdclk 2 the minimum time assumes a ?al sample period of 2 atd clocks cycles while the maximum time assumes a ?al sample period of 16 atd clocks. 3 reduced accuracy see table a-14 and table a-15 . n conv10 t conv10 t conv10 14 7 3.5 28 14 7 cycles s s 5 d atd 8-bit conversion period clock cycles 1 conv, time at 2.0mhz atd clock f atdclk n conv8 t conv8 12 6 26 13 cycles s 6 d stop recovery time (v dda =5.0 volts) t sr 20 s 7 p reference supply current (two atd modules) i ref 0.750 ma 8 p reference supply current (one atd module) i ref 0.375 ma appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 574 freescale semiconductor a.5.2 factors in?encing accuracy three factors ?source resistance, source capacitance and current injection ?have an in?ence on the accuracy of the atd. a.5.2.1 source resistance due to the input pin leakage current as speci?d in table a-6 and table a-7 in conjunction with the source resistance there will be a voltage drop from the signal source to the atd input. the maximum source resistance r s speci?s results in an error of less than 1/2 lsb (2.5mv) at the maximum leakage current. if device or operating conditions are less than worst case or leakage-induced error is acceptable, larger values of source resistance are allowed. a.5.2.2 source capacitance when sampling an additional internal capacitor is switched to the input. this can cause a voltage drop due to charge sharing with the external and the pin capacitance. for a maximum sampling error of the input voltage 1lsb, then the external ?ter capacitor, c f 1024 * (c ins ? inn ). table a-12. 3.3v atd operating characteristics conditions are shown in table a-4 unless otherwise noted; supply voltage 3.3v-10% <= v dda <= 3.3v+10% num c rating symbol min typ max unit 1 d reference potential low high v rl v rh v ssa v dda /2 v dda /2 v dda v v 2 c differential reference voltage v rh ? rl 3.0 3.3 3.6 v 3 d atd clock frequency f atdclk 0.5 2.0 mhz 4 d atd 10-bit conversion period clock cycles 1 conv, time at 2.0mhz atd clock f atdclk conv, time at 4.0mhz 2 atd clock f atdclk 1 the minimum time assumes a ?al sample period of 2 atd clocks cycles while the maximum time assumes a ?al sample period of 16 atd clocks. 2 reduced accuracy see table a-14 and table a-15 . n conv10 t conv10 t conv10 14 7 3.5 28 14 7 cycles s s 5 d atd 8-bit conversion period clock cycles 1 conv, time at 2.0mhz atd clock f atdclk n conv8 t conv8 12 6 26 13 cycles s 6 d recovery time (v dda =3.3 volts) t rec 20 s 7 p reference supply current (two atd modules) i ref 0.500 ma 8 p reference supply current (one atd module) i ref 0.250 ma appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 575 a.5.2.3 current injection there are two cases to consider. 1. a current is injected into the channel being converted. the channel being stressed has conversion values of $3ff ($ff in 8-bit mode) for analog inputs greater than vrh and $000 for values less than vrl unless the current is higher than speci?d as disruptive conditions. 2. current is injected into pins in the neighborhood of the channel being converted. a portion of this current is picked up by the channel (coupling ratio k), this additional current impacts the accuracy of the conversion depending on the source resistance. the additional input voltage error on the converted channel can be calculated as v err =k*r s * i inj , with i inj being the sum of the currents injected into the two pins adjacent to the converted channel. a.5.3 atd accuracy table a-14 and table a-15 specify the atd conversion performance excluding any errors due to current injection, input capacitance and source resistance. table a-13. atd electrical characteristics conditions are shown in table a-4 unless otherwise noted num rating symbol min typ max unit 1 max input source resistance r s 1k ? 2 total input capacitance non sampling sampling c inn c ins 10 22 pf 3 disruptive analog input current i na ?.5 2.5 ma 4 coupling ratio positive current injection k p 10 -4 a/a 5 coupling ratio negative current injection k n 10 -2 a/a table a-14. 5v atd conversion performance conditions are shown in table a-4 unless otherwise noted v ref = v rh - v rl = 5.12v. resulting to one 8 bit count = 20mv and one 10 bit count = 5m. vf atdclk = 2.0mhz num c rating symbol min typ max unit 1 p 10-bit resolution lsb 5 mv 2 p 10-bit differential nonlinearity dnl ? 1 counts 3 p 10-bit integral nonlinearity inl ?.5 1.5 2.5 counts 4 p 10-bit absolute error 1 1 these values include quantization error which is inherently 1/2 count for any a/d converter. ae ? 2.0 3 counts 5 c 10-bit absolute error at f atdclk = 4mhz ae 7.0 counts 6 p 8-bit resolution lsb 20 mv 7 p 8-bit differential nonlinearity dnl ?.5 0.5 counts 8 p 8-bit integral nonlinearity inl ?.0 0.5 1.0 counts 9 p 8-bit absolute error 1 ae ?.5 1.0 1.5 counts appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 576 freescale semiconductor for the following de?itions see also figure a-2 . differential non-linearity (dnl) is de?ed as the difference between two adjacent switching steps. the integral non-linearity (inl) is de?ed as the sum of all dnls: table a-15. 3.3v atd conversion performance conditions are shown in table a-4 unless otherwise noted v ref = v rh - v rl = 3.328v. resulting to one 8 bit count = 13mv and one 10 bit count = 3.25mv. f atdclk = 2.0mhz num c rating symbol min typ max unit 1 p 10-bit resolution lsb 3.25 mv 2 p 10-bit differential nonlinearity dnl ?.5 1.5 counts 3 p 10-bit integral nonlinearity inl ?.5 1.5 3.5 counts 4 p 10-bit absolute error 1 1 these values include the quantization error which is inherently 1/2 count for any a/d converter. ae ? 2.5 5 counts 5 c 10-bit absolute error at f atdclk = 4mhz ae 7.0 counts 6 p 8-bit resolution lsb 13 mv 7 p 8-bit differential nonlinearity dnl ?.5 counts 8 p 8-bit integral nonlinearity inl ?.5 0.1 1.5 counts 9 p 8-bit absolute error 1 ae ?.0 1.5 2.0 counts dnl i () v i v i1 1lsb -------------------------- - 1 = inl n () dnl i () i1 = n v n v 0 1lsb -------------------- - n == appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 577 figure a-2. atd accuracy de?itions note figure a-2 shows only de?itions, for speci?ation values refer to table a-14 and table a-15 . 1 5 vin mv 10 15 20 25 30 35 40 5085 5090 5095 5100 5105 5110 5115 5120 5065 5070 5075 5080 5060 0 3 2 5 4 7 6 50 $3f7 $3f9 $3f8 $3fb $3fa $3fd $3fc $3fe $3ff $3f4 $3f6 $3f5 8 9 1 2 $ff $fe $fd $3f3 10-bit resolution 8-bit resolution ideal transfer curve 10-bit transfer curve 8-bit transfer curve 5055 10-bit absolute error boundary 8-bit absolute error boundary lsb vi-1 vi dnl appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 578 freescale semiconductor a.6 nvm, flash and eeprom note unless otherwise noted the abbreviation nvm (non volatile memory) is used for both flash and eeprom. a.6.1 nvm timing the time base for all nvm program or erase operations is derived from the oscillator. a minimum oscillator frequency f nvmosc is required for performing program or erase operations. the nvm modules do not have any means to monitor the frequency and will not prevent program or erase operation at frequencies above or below the speci?d minimum. attempting to program or erase the nvm modules at a lower frequency a full program or erase transition is not assured. the flash and eeprom program and erase operations are timed using a clock derived from the oscillator using the fclkdiv and eclkdiv registers respectively. the frequency of this clock must be set within the limits speci?d as f nvmop . the minimum program and erase times shown in table a-16 are calculated for maximum f nvmop and maximum f bus . the maximum times are calculated for minimum f nvmop and a f bus of 2mhz. a.6.1.1 single word programming the programming time for single word programming is dependant on the bus frequency as a well as on the frequency f nvmop and can be calculated according to the following formula. a.6.1.2 row programming flash programming where up to 64 words in a row can be programmed consecutively by keeping the command pipeline ?led. the time to program a consecutive word can be calculated as: the time to program a whole row is: row programming is more than 2 times faster than single word programming. t swpgm 9 1 f nvmop ------------------------ - ? 25 1 f bus ----------- - ? + = t bwpgm 4 1 f nvmop ------------------------ - ? 9 1 f bus ----------- - ? + = t brpgm t swpgm 63 t bwpgm ? + = appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 579 a.6.1.3 sector erase erasing a 1024 byte flash sector or a 4 byte eeprom sector takes: the setup time can be ignored for this operation. a.6.1.4 mass erase erasing a nvm block takes: the setup time can be ignored for this operation. a.6.1.5 blank check the time it takes to perform a blank check on the flash or eeprom is dependant on the location of the ?st non-blank word starting at relative address zero. it takes one bus cycle per word to verify plus a setup of the command. table a-16. nvm timing characteristics conditions are shown in table a-4 unless otherwise noted num c rating symbol min typ max unit 1 d external oscillator clock f nvmosc 0.5 50 1 1 restrictions for oscillator in crystal mode apply! mhz 2 d bus frequency for programming or erase operations f nvmbus 1 mhz 3 d operating frequency f nvmop 150 200 khz 4 p single word programming time t swpgm 46 2 2 minimum programming times are achieved under maximum nvm operating frequency f nvmop and maximum bus frequency f bus . 74.5 3 3 maximum erase and programming times are achieved under particular combinations of f nvmop and bus frequency f bus . refer to formula in section a.6.1.1, ?ingle word programming and section a.6.1.4, ?ass erase for guidance. s 5 d flash burst programming consecutive word 4 4 burst programming operations are not applicable to eeprom t bwpgm 20.4 2 ?1 3 s 6 d flash burst programming time for 64 words 4 t brpgm 1331.2 2 2027.5 3 s 7 p sector erase time t era 20 5 5 minimum erase times are achieved under maximum nvm operating frequency f nvmop . 26.7 3 ms 8 p mass erase time t mass 100 5 133 3 ms 9 d blank check time flash per block t check 11 6 6 minimum time, if ?st word in the array is not blank 65546 7 7 maximum time to complete check on an erased block t cyc 10 d blank check time eeprom per block t check 11 6 2058 7 t cyc t era 4000 1 f nvmop ------------------------ - ? t mass 20000 1 f nvmop ------------------------ - ? t check location t cyc 10 t cyc ? + ? appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 580 freescale semiconductor a.6.2 nvm reliability the reliability of the nvm blocks is guaranteed by stress test during quali?ation, constant process monitors and burn-in to screen early life failures. the failure rates for data retention and program/erase cycling are speci?d at the operating conditions noted. the program/erase cycle count on the sector is incremented every time a sector or mass erase event is executed. note all values shown in table a-17 are target values and subject to further extensive characterization. table a-17. nvm reliability characteristics 1 1 t javg will not exeed 85 c considering a typical temperature pro?e over the lifetime of a consumer, industrial or automotive application. conditions are shown in table a-4 unless otherwise noted num c rating symbol min typ max unit 1 c data retention after 10,000 program/erase cycles at an average junction temperature of t javg 85 c t nvmret 15 100 2 2 typical data retention values are based on intrinsic capability of the technology measured at high temperature and de-rated to 25 c using the arrhenius equation. for additional information on how freescale de?es typical data retention, please refer to engineering bulletin eb618. years 2 c data retention with <100 program/erase cycles at an average junction temperature t javg 85 c 20 100 2 3 c flash number of program/erase cycles (?0 c t j 0 c) n flpe 10,000 cycles (0 c t j 140 c) 10,000 100,000 3 3 spec table quotes typical endurance evaluated at 25 c for this product family, typical endurance at various temperature can be estimated using the graph below. for additional information on how freescale de?es typical endurance, please refer to engineering bulletin eb619. 4 c eeprom number of program/erase cycles (?0 c t j 0 c) n eepe 10,000 cycles (0 c < t j 140 c) 100,000 300,000 3 cycles appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 581 a.7 reset, oscillator and pll this section summarizes the electrical characteristics of the various startup scenarios for oscillator and phase-locked-loop (pll). a.7.1 startup table a-18 summarizes several startup characteristics explained in this section. detailed description of the startup behavior can be found in the clock and reset generator (crg) block user guide. a.7.1.1 por the release level v porr and the assert level v pora are derived from the v dd supply. they are also valid if the device is powered externally. after releasing the por reset the oscillator and the clock quality check are started. if after a time t cqout no valid oscillation is detected, the mcu will start using the internal self clock. the fastest startup time possible is given by n uposc . a.7.1.2 sram data retention provided an appropriate external reset signal is applied to the mcu, preventing the cpu from executing code when vdd5 is out of speci?ation limits, the sram contents integrity is guaranteed if after the reset the porf bit in the crg flags register has not been set. a.7.1.3 external reset when external reset is asserted for a time greater than pw rstl the crg module generates an internal reset, and the cpu starts fetching the reset vector without doing a clock quality check, if there was an oscillation before reset. a.7.1.4 stop recovery out of stop the controller can be woken up by an external interrupt. a clock quality check as after por is performed before releasing the clocks to the system. table a-18. startup characteristics conditions are shown in table a-4 unless otherwise noted num c rating symbol min typ max unit 1 t por release level v porr 2.07 v 2 t por assert level v pora 0.97 v 3 d reset input pulse width, minimum input time pw rstl 2 t osc 4 d startup from reset n rst 192 196 n osc 5 d interrupt pulse width, irq edge-sensitive mode pw irq 20 ns 6 d wait recovery startup time t wrs 14 t cyc appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 582 freescale semiconductor a.7.1.5 pseudo stop and wait recovery the recovery from pseudo stop and wait are essentially the same since the oscillator was not stopped in both modes. the controller can be woken up by internal or external interrupts. after t wrs the cpu starts fetching the interrupt vector. a.7.2 oscillator the device features an internal low-power loop controlled pierce oscillator and a full swing pierce oscillator/external clock mode. the selection of loop controlled pierce oscillator or full swing pierce oscillator/external clock depends on the xclks signal which is sampled during reset. full swing pierce oscillator/external clock mode allows the input of a square wave. before asserting the oscillator to the internal system clocks the quality of the oscillation is checked for each start from either power-on, stop or oscillator fail. t cqout speci?s the maximum time before switching to the internal self clock mode after por or stop if a proper oscillation is not detected. the quality check also determines the minimum oscillator start-up time t uposc . the device also features a clock monitor. a clock monitor failure is asserted if the frequency of the incoming clock signal is below the assert frequency f cmfa . table a-19. oscillator characteristics conditions are shown in table a-4 unless otherwise noted num c rating symbol min typ max unit 1a c crystal oscillator range (loop controlled pierce) f osc 4.0 16 mhz 1b c crystal oscillator range (full swing pierce) 1,2 1 depending on the crystal a damping series resistor might be necessary 2 only valid if full swing pierce oscillator/external clock mode is selected f osc 0.5 40 mhz 2 p startup current i osc 100 a 3 c oscillator start-up time (loop controlled pierce) t uposc ? 3 3 f osc = 4mhz, c = 22pf. 50 4 4 maximum value is for extreme cases using high q, low frequency crystals ms 4 d clock quality check time-out t cqout 0.45 2.5 s 5 p clock monitor failure assert frequency f cmfa 50 100 200 khz 6 p external square wave input frequency f ext 0.5 50 mhz 7 d external square wave pulse width low t extl 9.5 ns 8 d external square wave pulse width high t exth 9.5 ns 9 d external square wave rise time t extr 1 ns 10 d external square wave fall time t extf 1 ns 11 d input capacitance (extal, xtal pins) c in ? pf 12 p extal pin input high voltage v ih,extal 0.75*v ddpll v t extal pin input high voltage v ih,extal v ddpll + 0.3 v 13 p extal pin input low voltage v il,extal 0.25*v ddpll v t extal pin input low voltage v il,extal v sspll ?0.3 v 14 c extal pin input hysteresis v hys,extal 250 mv appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 583 a.7.3 phase locked loop the oscillator provides the reference clock for the pll. the pll s voltage controlled oscillator (vco) is also the system clock source in self clock mode. a.7.3.1 xfc component selection this section describes the selection of the xfc components to achieve a good ?ter characteristics. figure a-3. basic pll functional diagram the following procedure can be used to calculate the resistance and capacitance values using typical values for k 1 , f 1 and i ch from table a-20 . the grey boxes show the calculation for f vco = 50mhz and f ref = 1mhz. e.g., these frequencies are used for f osc = 4mhz and a 25mhz bus clock. the vco gain at the desired vco frequency is approximated by: the phase detector relationship is given by: i ch is the current in tracking mode. the loop bandwidth f c should be chosen to ful?l the gardner s stability criteria by at least a factor of 10, typical values are 50. = 0.9 ensures a good transient response. and ?ally the frequency relationship is de?ed as fosc 1 refdv+1 fref phase detector vco kv 1 synr+1 fvco loop divider kf 1 2 d fcmp cs r cp vddpll xfc pin k v k 1 e f 1 f vco () k 1 1v ? --------------------------- - ? = 100 e 60 50 () 100 ---------------------- ? = = -90.48mhz/v k i ch k v ? = = 316.7hz/ ? appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 584 freescale semiconductor with the above values the resistance can be calculated. the example is shown for a loop bandwidth f c =10khz: the capacitance c s can now be calculated as: the capacitance c p should be chosen in the range of: a.7.3.2 jitter information note this section is under construction the basic functionality of the pll is shown in figure a-3 . with each transition of the clock f cmp , the deviation from the reference clock f ref is measured and input voltage to the vco is adjusted accordingly.the adjustment is done continuously with no abrupt changes in the clock output frequency. noise, voltage, temperature and other factors cause slight variations in the control loop resulting in a clock jitter. this jitter affects the real minimum and maximum clock periods as illustrated in figure a-4 . figure a-4. jitter de?itions n f vco f ref --------------- 2 synr 1 + () ? == = 50 f c 2 f ref ?? 1 2 + + ?? ?? ? ------------------------------------------ - 1 10 ----- - f c f ref 410 ? ------------- 0.9 = () ; < ? < f c < 25khz r 2 nf c ??? k ----------------------------- = =2* *50*10khz/(316.7hz/ ? ) =9.9k ? =~10k ? c s 2 2 ? f c r ?? ---------------------- 0.516 f c r ? -------------- - 0.9 = () ; = = 5.19nf =~ 4.7nf c s 20 ? c p c s 10 ? ? c p = 470pf 2 3 n-1 n 1 0 t nom t max1 t min1 t maxn t minn appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 585 the relative deviation of t nom is at its maximum for one clock period, and decreases towards zero for larger number of clock periods (n). appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 586 freescale semiconductor de?ing the jitter as: note from the evaluation data a formula for t max = f(n), resp. t min = f(n) should be derived. assuming no long term drift of the reference clock, the following will hold this is very important to notice with respect to timers, serial modules where a pre-scaler will eliminate the effect of the jitter to a large extent. table a-20. pll characteristics conditions are shown in table a-4 unless otherwise noted num c rating symbol min typ max unit 1 p self clock mode frequency f scm 1 5.5 mhz 2 d vco locking range f vco 8 50 mhz 3 d lock detector transition from acquisition to tracking mode ? trk 3% 4% 1 1 % deviation from target frequency 4 d lock detection ? lock 0% 1.5% 1 5 d un-lock detection ? unl 0.5% 2.5% 1 6 d lock detector transition from tracking to acquisition mode ? unt 6% 8% 1 7 c pllon total stabilization delay 2 2 f osc = 4mhz, f bus = 25mhz equivalent f vco = 50mhz: refdv = #$03, synr = #$018, cs = 4.7nf, cp = 470pf, rs = 10k ? . t stab 0.5 ms 8 d pllon acquisition mode stabilization delay 2 t acq 0.3 ms 9 d pllon tracking mode stabilization delay 2 t al 0.2 ms 10 d fitting parameter vco loop gain k 1 ?00 mhz/v 11 d fitting parameter vco loop frequency f 1 60 mhz 12 d charge pump current acquisition mode i ch ?8.5 a 13 d charge pump current tracking mode i ch ?3.5 a 14 c jitter ? parameter 1 2 j 1 1.1 % 15 c jitter ? parameter 2 2 j 2 0.13 % jn () max 1 t max n () nt nom ? ---------------------- - 1 t min n () nt nom ? ---------------------- - , ?? ?? ?? = jn () n lim 0 = appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 587 a.8 mscan a.9 spi a.9.1 master mode figure a-5 and figure a-6 illustrate the master mode timing. timing values are shown in table a-22 . figure a-5. spi master timing (cpha = 0) table a-21. mscan wake-up pulse characteristics conditions are shown in table a-4 unless otherwise noted num c rating symbol min typ max unit 1 p mscan wake-up dominant pulse ?tered t wup 2 s 2 p mscan wake-up dominant pulse pass t wup 5 s sck (output) sck (output) miso (input) mosi (output) ss 1 (output) 1 9 5 6 msb in2 bit 6 . . . 1 lsb in msb out2 lsb out bit 6 . . . 1 10 4 4 2 9 (cpol = 0) (cpol = 1) 3 11 12 1. if con?ured as an output. 2. lsbf = 0. for lsbf = 1, bit order is lsb, bit 1, ..., bit 6, msb. appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 588 freescale semiconductor figure a-6. spi master timing (cpha =1) table a-22. spi master mode timing characteristics conditions are shown in table a-4 unless otherwise noted, cload = 200pf on all outputs num c rating symbol min typ max unit 1 p operating frequency f op dc 1 / 4f bus 1 p sck period t sck 4 2048 t bus 2 d enable lead time t lead 1 / 2 t sck 3 d enable lag time t lag 1 / 2 t sck 4 d clock (sck) high or low time t wsck t bus ? 30 1024 t bus ns 5 d data setup time (inputs) t su 25 ns 6 d data hold time (inputs) t hi 0 ns 9 d data valid (after sck edge) t v 25 ns 10 d data hold time (outputs) t ho 0 ns 11 d rise time inputs and outputs t r 25 ns 12 d fall time inputs and outputs t f 25 ns sck (output) sck (output) miso (input) mosi (output) 1 5 6 msb in2 bit 6 . . . 1 lsb in master msb out2 master lsb out bit 6 . . . 1 4 4 9 11 12 10 port data (cpol = 0) (cpol = 1) port data ss 1 (output) 2 12 11 3 1. if con?ured as output 2. lsbf = 0. for lsbf = 1, bit order is lsb, bit 1, ..., bit 6, msb. appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 589 a.9.2 slave mode figure a-7 and figure a-8 illustrate the slave mode timing. timing values are shown in table a-23 . figure a-7. spi slave timing (cpha = 0) figure a-8. spi slave timing (cpha =1) sck (input) sck (input) mosi (input) miso (output) ss (input) 1 9 5 6 msb in bit 6 . . . 1 lsb in msb out slave lsb out bit 6 . . . 1 10 4 4 2 7 (cpol = 0) (cpol = 1) 3 12 note: not de?ed but normally msb of character just received. slave 12 11 10 see 11 note 8 sck (input) sck (input) mosi (input) miso (output) 1 5 6 msb in bit 6 . . . 1 lsb in msb out slave lsb out bit 6 . . . 1 4 4 9 11 12 10 see (cpol = 0) (cpol = 1) ss (input) 2 12 11 3 note: not de?ed but normally lsb of character just received. slave note 7 8 appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 590 freescale semiconductor a.10 external bus timing a timing diagram of the external multiplexed-bus is illustrated in figure a-9 with the actual timing values shown on table table a-24 . all major bus signals are included in the diagram. while both a data write and data read cycle are shown, only one or the other would occur on a particular bus cycle. a.10.1 general muxed bus timing the expanded bus timings are highly dependent on the load conditions. the timing parameters shown assume a balanced load across all outputs. table a-23. spi slave mode timing characteristics conditions are shown in table a-4 unless otherwise noted, cload = 200pf on all outputs num c rating symbol min typ max unit 1 p operating frequency f op dc 1 / 4f bus 1 p sck period t sck 4 2048 t bus 2 d enable lead time t lead 1 t cyc 3 d enable lag time t lag 1 t cyc 4 d clock (sck) high or low time t wsck t cyc ? 30 ns 5 d data setup time (inputs) t su 25 ns 6 d data hold time (inputs) t hi 25 ns 7 d slave access time t a 1t cyc 8 d slave miso disable time t dis 1t cyc 9 d data valid (after sck edge) t v 25 ns 10 d data hold time (outputs) t ho 0 ns 11 d rise time inputs and outputs t r 25 ns 12 d fall time inputs and outputs t f 25 ns appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 591 figure a-9. general external bus timing addr/data (read) addr/data (write) addr data data 5 10 11 8 16 6 eclk 1, 2 3 4 addr data data 12 15 9 7 14 13 ecs 21 20 22 23 non-multiplexed 17 19 lstrb 29 noacc 32 pipo0 pipo1, pe6,5 35 18 27 28 30 33 36 31 34 r/w 24 26 25 addresses pe4 pa, pb pa, pb pk5:0 pk7 pe2 pe3 pe7 appendix a electrical characteristics mc9s12kg128 data sheet, rev. 1.15 592 freescale semiconductor table a-24. expanded bus timing characteristics conditions are shown in table a-4 unless otherwise noted, c load = 50pf num c rating symbol min typ max unit 1 p frequency of operation (e-clock) f o 0 25.0 mhz 2 p cycle time t cyc 40 ns 3 d pulse width, e low pw el 17 ns 4 d pulse width, e high 1 1 affected by clock stretch: add n x t cyc where n=0,1,2 or 3, depending on the number of clock stretches. pw eh 17 ns 5 d address delay time t ad 8ns 6 d address valid time to e rise (pw el ? ad )t av 11 ns 7 d muxed address hold time t mah 2 ns 8 d address hold to data valid t ahds 7 ns 9 d data hold to address t dha 2 ns 10 d read data setup time t dsr 13 ns 11 d read data hold time t dhr 0 ns 12 d write data delay time t ddw 7ns 13 d write data hold time t dhw 2 ns 14 d write data setup time 1 (pw eh ? ddw )t dsw 10 ns 15 d address access time 1 (t cyc ? ad ? dsr )t acca 19 ns 16 d e high access time 1 (pw eh ? dsr )t acce 4 ns 17 d non-multiplexed address delay time t nad 7ns 18 d non-muxed address valid to e rise (pw el ? nad )t nav 10 ns 19 d non-multiplexed address hold time t nah 2 ns 20 d chip select delay time t csd 16 ns 21 d chip select access time 1 (t cyc ? csd ? dsr )t accs 11 ns 22 d chip select hold time t csh 2 ns 23 d chip select negated time t csn 8 ns 24 d read/write delay time t rwd 7ns 25 d read/write valid time to e rise (pw el ? rwd )t rwv 10 ns 26 d read/write hold time t rwh 2 ns 27 d low strobe delay time t lsd 7ns 28 d low strobe valid time to e rise (pw el ? lsd )t lsv 10 ns 29 d low strobe hold time t lsh 2 ns 30 d noacc strobe delay time t nod 7ns 31 d noacc valid time to e rise (pw el ? lsd )t nov 10 ns 32 d noacc hold time t noh 2 ns 33 d pipo0 delay time t p0d 2?ns 34 d pipo0 valid time to e rise (pw el ? p0d )t p0v 10 ns 35 d pipo1 delay time 1 (pw eh -t p1v )t p1d 2?ns 36 d pipo1 valid time to e fall t p1v 10 ns appendix b recommended pcb layout mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 593 appendix b recommended pcb layout figure b-1. recommended pcb layout for 112lqfp c5 c4 c1 c6 c3 c2 c10 c9 r1 vddx vssx vddr vssr vdd1 vss1 vdd2 vss2 vddpll vsspll vdda vssa vregen c7 c8 q1 appendix b recommended pcb layout mc9s12kg128 data sheet, rev. 1.15 594 freescale semiconductor figure b-2. recommended pcb layout for 80qfp c5 c4 c3 c2 c10 c9 r1 c6 c1 vdd1 vss1 vss2 vdd2 vssr vddr vsspll vddpll vdda vssa vssx vregen vddx c7 c8 q1 vsspll appendix b recommended pcb layout mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 595 the pcb must be carefully laid out to ensure proper operation of the voltage regulator as well as of the mcu itself{statement}. the following rules must be observed: every supply pair must be decoupled by a ceramic capacitor connected as near as possible to the corresponding pins (c1 - c6). central point of the ground star should be the vssr pin. use low ohmic low inductance connections between vss1, vss2 and vssr. vsspll must be directly connected to vssr. keep traces of vsspll, extal and xtal as short as possible and occupied board area for c7, c8 and q1 as small as possible. do not place other signals or supplies underneath area occupied by c7, c8 and q1 and the connection area to the mcu. central power input should be fed in at the vdda/vssa pins. table b-1. recommended components component purpose type value c1 vdd1 ?ter cap ceramic x7r 400nf c2 vdd2 ?ter cap (80 qfp only) ceramic x7r 400nf c3 vdda ?ter cap ceramic x7r 100nf c4 vddr ?ter cap x7r/tantalum >=100nf c5 vddpll ?ter cap ceramic x7r 200nf c6 vddx ?ter cap x7r/tantalum >=100nf c7 osc load cap c8 osc load cap c9 pll loop ?ter cap see pll speci?ation chapter c10 pll loop ?ter cap r1 pll loop ?ter res q1 quartz appendix c package information mc9s12kg128 data sheet, rev. 1.15 596 freescale semiconductor appendix c package information this section provides the physical dimensions of the mc9s12kg128 packages. appendix c package information mc9s12kg128 data sheet, rev. 1.15 freescale semiconductor 597 c.1 112-pin lqfp package figure c-1. 112-pin lqfp mechanical dimensions (case no. 987) dim a min max 20.000 bsc millimeters a1 10.000 bsc b 20.000 bsc b1 10.000 bsc c --- 1.600 c1 0.050 0.150 c2 1.350 1.450 d 0.270 0.370 e 0.450 0.750 f 0.270 0.330 g 0.650 bsc j 0.090 0.170 k 0.500 ref p 0.325 bsc r1 0.100 0.200 r2 0.100 0.200 s 22.000 bsc s1 11.000 bsc v 22.000 bsc v1 11.000 bsc y 0.250 ref z 1.000 ref aa 0.090 0.160 11 11 13 7 13 view y l-m 0.20 n t 4x 4x 28 tips pin 1 ident 1 112 85 84 28 57 29 56 b v v1 b1 a1 s1 a s view ab 0.10 3 c c2 2 0.050 seating plane gage plane 1 view ab c1 (z) (y) e (k) r2 r1 0.25 j1 view y j1 p g 108x 4x section j1-j1 base rotated 90 counterclockwise metal j aa f d l-m m 0.13 n t 1 2 3 c l l-m 0.20 n t l n m t t 112x x x=l, m or n r r notes: 1. dimensioning and tolerancing per asme y14.5m, 1994. 2. dimensions in millimeters. 3. datums l, m and n to be determined at seating plane, datum t. 4. dimensions s and v to be determined at seating plane, datum t. 5. dimensions a and b do not include mold protrusion. allowable protrusion is 0.25 per side. dimensions a and b include mold mismatch. 6. dimension d does not include dambar protrusion. allowable dambar protrusion shall not cause the d dimension to exceed 0.46. 8 3 0 appendix c package information mc9s12kg128 data sheet, rev. 1.15 598 freescale semiconductor c.2 80-pin qfp package figure c-2. 80-pin qfp mechanical dimensions (case no. 841b) notes: 1. dimensioning and tolerancing per ansi y14.5m, 1982. 2. controlling dimension: millimeter. 3. datum plane -h- is located at bottom of lead and is coincident with the lead where the lead exits the plastic body at the bottom of the parting line. 4. datums -a-, -b- and -d- to be determined at datum plane -h-. 5. dimensions s and v to be determined at seating plane -c-. 6. dimensions a and b do not include mold protrusion. allowable protrusion is 0.25 per side. dimensions a and b do include mold mismatch and are determined at datum plane -h-. 7. dimension d does not include dambar protrusion. allowable dambar protrusion shall be 0.08 total in excess of the d dimension at maximum material condition. dambar cannot be located on the lower radius or the foot. section b-b 61 60 detail a l 41 40 80 -a- l -d- a s a-b m 0.20 d s h 0.05 a-b s 120 21 -b- b v j f n d view rotated 90 detail a b b p -a-,-b-,-d- e h g m m detail c seating plane -c- c datum plane 0.10 -h- datum plane -h- u t r q k w x detail c dim min max millimeters a 13.90 14.10 b 13.90 14.10 c 2.15 2.45 d 0.22 0.38 e 2.00 2.40 f 0.22 0.33 g 0.65 bsc h --- 0.25 j 0.13 0.23 k 0.65 0.95 l 12.35 ref m 510 n 0.13 0.17 p 0.325 bsc q 07 r 0.13 0.30 s 16.95 17.45 t 0.13 --- u 0 --- v 16.95 17.45 w 0.35 0.45 x 1.6 ref s a-b m 0.20 d s c s a-b m 0.20 d s h 0.05 d s a-b m 0.20 d s c s a-b m 0.20 d s c how to reach us: home page: www.freescale.com usa/europe or locations not listed: freescale semiconductor technical information center, ch370 1300 n. alma school road chandler, arizona 85224 1-800-521-6274 or 480-768-2130 europe, middle east, and africa: +44 1296 380 456 (english) +46 8 52200080 (english) +49 89 92103 559 (german) +33 1 69 35 48 48 (french) japan: freescale semiconductor japan ltd. technical information center 3-20-1, minami-azabu, minato-ku tokyo 106-0047, japan 0120-191014 or +81-3-3440-3569 asia/paci?: freescale semiconductor hong kong ltd. technical information center 2 dai king street tai po industrial estate tai po, n.t., hong kong 852-26668334 for literature requests only: freescale semiconductor literature distribution center p.o. box 5405 denver, colorado 80217 1-800-441-2447 or 303-675-2140 fax: 303-675-2150 freescale and the freescale logo are trademarks of freescale semiconductor, inc. all other product or service names are the property of their respective owners. the arm powered logo is a registered trademark of arm limited. arm7tdmi-s is a trademark of arm limited. java and all other java-based marks are trademarks or registered trademarks of sun microsystems, inc. in the u.s. and other countries. the bluetooth trademarks are owned by their proprietor and used by freescale semiconductor, inc. under license. ?freescale semiconductor, inc. 2005. all rights reserved. mc9s12kg128v1 rev. rev. 1.15 06/2006 information in this document is provided solely to enable system and software implementers to use freescale semiconductor products. there are no express or implied copyright licenses granted hereunder to design or fabricate any integrated circuits or integrated circuits based on the information in this document. freescale semiconductor reserves the right to make changes without further notice to any products herein. freescale semiconductor makes no warranty, representation or guarantee regarding the suitability of its products for any particular purpose, nor does freescale semiconductor assume any liability arising out of the application or use of any product or circuit, and speci?ally disclaims any and all liability, including without limitation consequential or incidental damages. typical parameters that may be provided in freescale semiconductor data sheets and/or speci?ations can and do vary in different applications and actual performance may vary over time. all operating parameters, including ?ypicals? must be validated for each customer application by customer s technical experts. freescale semiconductor does not convey any license under its patent rights nor the rights of others. freescale semiconductor products are not designed, intended, or authorized for use as components in systems intended for surgical implant into the body, or other applications intended to support or sustain life, or for any other application in which the failure of the freescale semiconductor product could create a situation where personal injury or death may occur. should buyer purchase or use freescale semiconductor products for any such unintended or unauthorized application, buyer shall indemnify and hold freescale semiconductor and its of?ers, employees, subsidiaries, af?iates, and distributors harmless against all claims, costs, damages, and expenses, and reasonable attorney fees arising out of, directly or indirectly, any claim of personal injury or death associated with such unintended or unauthorized use, even if such claim alleges that freescale semiconductor was negligent regarding the design or manufacture of the part. |
Price & Availability of MC9S12KC64CPV
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |